Bug 1898777

Summary: Need to configure optimum inode table hash_size for shd
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Mohit Agrawal <moagrawa>
Component: coreAssignee: Mohit Agrawal <moagrawa>
Status: CLOSED ERRATA QA Contact: Sayalee <saraut>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: lgangava, pprakash, puebele, rhs-bugs, sajmoham, saraut, sheggodu, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.5.z Batch Update 4   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: glusterfs-6.0-50 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-29 07:21:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mohit Agrawal 2020-11-18 03:54:35 UTC 
In brick_mux environment a shd process consume high memory.
After print the statedump i have found it allocates 1M per afr xlator for all bricks.In case of configure 4k volumes it consumes almost total 6G RSS size in which 4G consumes by inode_tables

[cluster/replicate.test1-replicate-0 - usage-type gf_common_mt_list_head memusage]
size=1273488
num_allocs=2
max_size=1273488
max_num_allocs=2
total_allocs=2

In inode_new_table we do allocate memory(1M) for a list of inode and dentry hash.
I believe in case of shd we do pass lru_limit size is 1 so we don't need to create a big hash table so optimize inode_table size for shd to reduce memory
consumption for shd process.
Comment 1 Mohit Agrawal 2020-11-18 03:56:22 UTC 
The upstream committed patch link
https://github.com/gluster/glusterfs/issues/1538
Comment 2 Mohit Agrawal 2020-11-18 03:57:27 UTC 
Need to backport this patch(inode_change) https://review.gluster.org/#/c/glusterfs/+/22184/ also in 
downstream at the time of merging previous patch otherwise shd will crash.
Comment 23 errata-xmlrpc 2021-04-29 07:21:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (glusterfs bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1462