[Bugs] [Bug 1738878] FUSE client's memory leak

[bugzilla at redhat.com]

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

Nithya Balachandran <nbalacha at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(s.pleshkov at hostco
                   |                            |.ru)



--- Comment #14 from Nithya Balachandran <nbalacha at redhat.com> ---
>From the statedump:




[mount/fuse.fuse - usage-type gf_fuse_mt_iov_base memusage]
size=117432480
num_allocs=212740
--


This is likely due to the bug that was fixed in
https://review.gluster.org/#/c/glusterfs/+/23016/. This fix needs to be
backported to release-6 as well.


The lru-limit has been set to 65000 so there are still over 65K inodes in
memory. Those will not be freed until the entries are deleted or the client is
remounted. The memory for these inodes, dentries and associated information for
various xlators will use up memory.

[nbalacha at dhcp35-62 Downloads]$ grep -A3 -B3 lru_size
glusterdump.6947.dump.1567662323 
xlator.mount.fuse.itable.name=meta-autoload/inode
xlator.mount.fuse.itable.lru_limit=65000
xlator.mount.fuse.itable.active_size=4613
xlator.mount.fuse.itable.lru_size=64996
xlator.mount.fuse.itable.purge_size=0
xlator.mount.fuse.itable.invalidate_size=0


You could reduce the lru-limit value further - that will lower the maximum
number of inodes in memory and the associated structures various xlators create
per inode.


For the dict_t , we will need more information before we can proceed. Do you
have a test script that reproduces the problem?

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