<div dir="ltr">Christian,<div><br></div><div>To debug memory leaks, we need periodic statedumps of respective processes. Please provide the statedumps.</div><div><br></div><div>I suspect that you are hitting <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1694612">https://bugzilla.redhat.com/show_bug.cgi?id=1694612</a>. This bug is addressed in release-5.6</div><div><br></div><div>Thanks,</div><div>Sanju</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jul 18, 2019 at 1:30 PM Christian Meyer <<a href="mailto:chrmeyer@chrmeyer.de">chrmeyer@chrmeyer.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi everyone!<br>
<br>
I'm using a Gluster 5.4 Setup with 3 Nodes with three volumes<br>
(replicated) (one is the gluster shared storage).<br>
Each node has 64GB of RAM.<br>
Over the time of ~2 month the memory consumption of glusterd grow<br>
linear. An the end glusterd used ~45% of RAM the brick processes<br>
together ~43% of RAM.<br>
I think this is a memory leak.<br>
<br>
I made a coredump of the processes (glusterd, bricks) (zipped ~500MB),<br>
hope this will help you to find the problem.<br>
<br>
Could you please have a look on it?<br>
<br>
Download Coredumps:<br>
<a href="https://s3.eu-central-1.amazonaws.com/glusterlogs/gluster_coredump.zip" rel="noreferrer" target="_blank">https://s3.eu-central-1.amazonaws.com/glusterlogs/gluster_coredump.zip</a><br>
<br>
Kind regards<br>
<br>
Christian<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Thanks,<br></div>Sanju<br></div></div>