Created attachment 1105748 [details] Statedumps for both server and client Description of problem: Fuse client appears to be building a large number of threads and the shared pool of ram? appears to be consuming more than is allocated and is failing to release memory. This server's uptime has only been 19 days so the amount of memory leakage appears somewhat substantial. Version-Release number of selected component (if applicable): sudo dpkg -l | grep gluster ii glusterfs-client 3.7.6-ubuntu1~trusty1 amd64 clustered file-system (client package) ii glusterfs-common 3.7.6-ubuntu1~trusty1 amd64 GlusterFS common libraries and translator modules How reproducible: Unsure Steps to Reproduce: 1. Create a 500GB 3-way replicated with quorum 2 (fixed) enabled. 2. Load it up with lots of small files (1kb - 50 kb) to about 55% full (not all files are this small, but the primary file type are PHP scripts). 3. Run it for an extended period of time doing the typical actions -- replace entire directories, symlink, rsync periodically for backups (READ FROM Gluster). Actual results: Memory leaking? Memory consumption is very high to the point of swapping. Rebooting the client clears the issue. Expected results: Not memory leaking? Additional info: Ubuntu 14.04 sudo cat gluster-glusterfs-3_7-trusty.list deb http://ppa.launchpad.net/gluster/glusterfs-3.7/ubuntu trusty main
Thanks Jack for attaching statedump.
Jack, I looked at the statedump for the client and didn't find anything out of the ordinary :-(. I just wanted you to confirm that the statedump is taken at the time when you observed huge memory usage by the client process. Pranith
Yes it was. I walked him through data collection before he restarted.
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.