<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 22, 2016 at 9:03 PM, Zdenek Styblik <span dir="ltr"><<a href="mailto:zdenek.styblik@showmax.com" target="_blank">zdenek.styblik@showmax.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sat, Aug 20, 2016 at 11:48 AM, Pranith Kumar Karampuri<br>
<<a href="mailto:pkarampu@redhat.com">pkarampu@redhat.com</a>> wrote:<br>
> hi Zdenek,<br>
> I recently found this issue and there has been a discussion on<br>
> gluster-devel about how to fix this. It is a bit involved, so taking more<br>
> time than I would like to fix, this bug has been there for almost 3-4 years<br>
> I guess.<br>
><br>
> You can find the discussion here:<br>
> <a href="http://www.gluster.org/pipermail/gluster-devel/2016-July/050085.html" rel="noreferrer" target="_blank">http://www.gluster.org/<wbr>pipermail/gluster-devel/2016-<wbr>July/050085.html</a><br>
><br>
<br>
</span>Hello Pranith,<br>
<br>
thank you for reply and heads up. I've read only through mails with<br>
subject "memory leak" and didn't know you, or somebody else, already<br>
found this issue.<br></blockquote><div><br></div><div>Hey,<br></div><div> Please err on posting these kinds of mails in future as well :-). In the worst case it will be something we already know. But in the best case it wll be something new :-).<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Best regards,<br>
Z.<br>
<div class="HOEnZb"><div class="h5"><br>
> On Fri, Aug 19, 2016 at 7:10 PM, Zdenek Styblik <<a href="mailto:zdenek.styblik@showmax.com">zdenek.styblik@showmax.com</a>><br>
> wrote:<br>
>><br>
>> Hello,<br>
>><br>
>> we've found a memory leak in glusterd v3.7.x(currently at v3.7.14, but<br>
>> we are users of v3.7.x from the beginning).<br>
>> It seems, we've empirically verified, that continuous execution of %<br>
>> gluster volume set <volname> <key> <value>; leads to memory leaks in<br>
>> glusterd and OOM, although not necessarily OOM of glusterd itself.<br>
>> Settings which were being set over and over again are<br>
>> `nfs.addr-namelookup false` and `nfs.disable true`. There might have<br>
>> been other settings, but I was able to find these in recent logs.<br>
>> Unfortunately, we don't have capacity to debug this issue<br>
>> further(statedumps are quite overwhelming :] ).<br>
>> Repeated execution has been caused due to bug in Puppet module we're<br>
>> using(and we were able to address this issue). Therefore, it's safe to<br>
>> say that the number of affected users or like hood of somebody else<br>
>> having these problem is probably low. It's still a memory leak and,<br>
>> well, rather serious one if you happen to stumble upon it. Also, it<br>
>> must be noted that this gets amplified if you have more than just<br>
>> volume.<br>
>><br>
>> If there is anything I can help with, let me know.<br>
>><br>
>> Please, keep me on CC as I'm not subscribed to the mailing list.<br>
>><br>
>> Best regards,<br>
>> Zdenek Styblik<br>
>> ______________________________<wbr>_________________<br>
>> Gluster-users mailing list<br>
>> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
>> <a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Pranith<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div>