I took a quick look at the builders and noticed both have the same error of
'Cannot allocate memory' which comes up every time when the builder is
rebooted after a build abort. It is happening in the same pattern. Though
there's no such memory consumption on the builders.
I’m investigating more on
On Wed, May 8, 2019 at 7:38 PM Atin Mukherjee wrote:
> builder204 needs to be fixed, too many failures, mostly none of the
> patches are passing regression.
>
And with that builder201 joins the pool,
https://build.gluster.org/job/centos7-regression/5943/consoleFull
> On Wed, May 8, 2019 at 9:5
Thanks!!
On Thu, May 9, 2019 at 8:34 AM Zhou, Cynthia (NSB - CN/Hangzhou) <
cynthia.z...@nokia-sbell.com> wrote:
> Hi,
>
> Ok, It is posted to https://review.gluster.org/#/c/glusterfs/+/22687/
>
>
>
>
>
>
>
> *From:* Raghavendra Gowdappa
> *Sent:* Wednesday, May 08, 2019 7:35 PM
> *To:* Zhou, Cy
Hi,
Ok, It is posted to https://review.gluster.org/#/c/glusterfs/+/22687/
From: Raghavendra Gowdappa
Sent: Wednesday, May 08, 2019 7:35 PM
To: Zhou, Cynthia (NSB - CN/Hangzhou)
Cc: Amar Tumballi Suryanarayan ; gluster-devel@gluster.org
Subject: Re: [Gluster-devel] glusterfsd memory leak issue
builder204 needs to be fixed, too many failures, mostly none of the patches
are passing regression.
On Wed, May 8, 2019 at 9:53 AM Atin Mukherjee wrote:
>
>
> On Wed, May 8, 2019 at 7:16 AM Sanju Rakonde wrote:
>
>> Deepshikha,
>>
>> I see the failure here[1] which ran on builder206. So, we are
On Wed, May 8, 2019 at 1:29 PM Zhou, Cynthia (NSB - CN/Hangzhou) <
cynthia.z...@nokia-sbell.com> wrote:
> Hi 'Milind Changire' ,
>
> The leak is getting more and more clear to me now. the unsolved memory
> leak is because of in gluterfs version 3.12.15 (in my env)the ssl context
> is a shared one,
awesome! well done!
thank you for taking pain to fix the memory leak
On Wed, May 8, 2019 at 1:28 PM Zhou, Cynthia (NSB - CN/Hangzhou) <
cynthia.z...@nokia-sbell.com> wrote:
> Hi 'Milind Changire' ,
>
> The leak is getting more and more clear to me now. the unsolved memory
> leak is because of in
Hi 'Milind Changire' ,
The leak is getting more and more clear to me now. the unsolved memory leak is
because of in gluterfs version 3.12.15 (in my env)the ssl context is a shared
one, while we do ssl_acept, ssl will allocate some read/write buffer to ssl
object, however, ssl_free in socket_rese
On Wed, May 8, 2019 at 12:08 AM Niels de Vos wrote:
> On Tue, May 07, 2019 at 11:37:27AM -0700, Vijay Bellur wrote:
> > On Tue, May 7, 2019 at 11:15 AM FNU Raghavendra Manjunath <
> rab...@redhat.com>
> > wrote:
> >
> > >
> > > + 1 to this.
> > >
> >
> > I have updated the footer of gluster-devel
On Tue, May 07, 2019 at 11:37:27AM -0700, Vijay Bellur wrote:
> On Tue, May 7, 2019 at 11:15 AM FNU Raghavendra Manjunath
> wrote:
>
> >
> > + 1 to this.
> >
>
> I have updated the footer of gluster-devel. If that looks ok, we can extend
> it to gluster-users too.
>
> In case of a month with 5
10 matches
Mail list logo