[Bugs] [Bug 1291479] New: Memory leak on Fuse client

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1291479

            Bug ID: 1291479
           Summary: Memory leak on Fuse client
           Product: GlusterFS
           Version: 3.7.6
         Component: fuse
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: jack.peterson at gmail.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Created attachment 1105748
  --> https://bugzilla.redhat.com/attachment.cgi?id=1105748&action=edit
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

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.