I've got a memory leak that I'm not entirely sure how to reproduce.
This is v3.4.4 with http://review.gluster.org/8029
Perhaps a duplicate of bz 1112844?
Created attachment 924419 [details]
compute021 dump file
Created attachment 924569 [details]
glusterdump of my client
This 3.4.4 client had consumed ~20 GB of RAM when I triggered the dump.
ReL: Perhaps a duplicate of bz 1112844?
1112844 was fixed in 3.4.5. Are you still experiencing the leak with 3.4.5?
Yes, still leaking with 3.4.5.
3.4.5 actually solved our memory leak problem.
*** Bug 1023191 has been marked as a duplicate of this bug. ***
*** Bug 1165429 has been marked as a duplicate of this bug. ***
GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5.
This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "email@example.com".
If there is no response by the end of the month, this bug will get automatically closed.
In past few months I have been running version 3.5.2 and issue existed. Note how much memory was committed when glusterd was left running for a new months, almost 350GB!
Last week, upgrade was done to version 3.7.3 and so far looks like not change, process glusterd keeps committing memory.
GlusterFS 3.4.x has reached end-of-life.
If this bug still exists in a later release please reopen this and change the version or open a new bug.
Bug still exists:
glusterfs 3.7.6 built on Nov 9 2015 15:19:41
17.7g 13g 1136 S 4.2 88.6 6301:05 glusterfs
Currently in use @ 1 of 4 nodes. Other nodes are running fine but based on swapping the performance drops.
Bug still exists for us too:
$ glusterfs --version
glusterfs 3.6.3 built on Apr 23 2015 16:12:23
server:/glusvol on /mnt/glusterfs type fuse.glusterfs (rw,allow_other,max_read=131072)
this mount, using a single glusterfs process will use up to the full 64Gb of RAM over around a week period. Then swapping starts, and users report slow performance and pausing. We need to log all users off the file share, umount and mount the volume and the memory comes back.
Is there any files I can send to help you guys analyze the issue?
Warm Regards, Neil
We are at 3.5.7 and see the same problem. It seems that it deallocates some when memory utilization is high. However, we have seen that it is not fast enough for the OOM, which will go ahead and kill glusterfs.
We will start some 3.7 testing soon.
Cheers, Hans Henrik
3.6.9 is the latest 3.6 release. You should start by testing from there.
Same goes for the 3.5 report, please test against 3.5.9.
Well, the changes between 3.5.7 to 3.5.9 does not indicate a fix. Also, the community releases still has 3.5.7 as LATEST.
Why shouldn't we test 3.7 instead of 3.6? It will be a separate test system.
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.
Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.