<div dir="ltr"><div><div>I'm aware of 2 different kinds of memory leaks on 3.3.1, one is in geo-replication and another one is native client side memory leak.<br></div>Sadly both got mixed in <a href="https://bugzilla.redhat.com/show_bug.cgi?id=841617">https://bugzilla.redhat.com/show_bug.cgi?id=841617</a><br>
<br></div>I can tell you that geo-replication leak is still present in 3.4.0 and native client leak isn't but I don't know what patch you need to backport :(<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Sep 11, 2013 at 1:16 PM, John Ewing <span dir="ltr"><<a href="mailto:johnewing1@gmail.com" target="_blank">johnewing1@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi,<div><br></div><div>I am using gluster 3.3.1 on Centos 6, installed from the glusterfs-3.3.1-1.el6.x86_64.rpm rpms.</div><div>I am seeing the Committed_AS memory continually increasing and the processes using the memory are glusterfsd instances.</div>
<div><br></div><div>see <a href="http://imgur.com/K3dalTW" target="_blank">http://imgur.com/K3dalTW</a> for graph.</div><div><br></div><div>Both nodes are exhibiting the same behaviour, I have tried the suggested </div><div>
<br></div><div>
echo 2 > /proc/sys/vm/drop_caches<br></div><div><br></div><div>but it made no difference. It there a known issue with 3.3.1 ?</div><div><br></div><div>Thanks</div><span class="HOEnZb"><font color="#888888"><div><br></div>
<div>John</div><div><br></div><div><br></div>
</font></span></div>
<br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br></blockquote></div><br></div>