Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: There are three parameters in configuration files which is better to be changed change the following i) up_poll_usec in FSAL{} in export conf file -- current value default 10us, better to change into 1ms Reason -- it impact cpu utilization of ganesha process, higher the interval lower cpu utiliization Patch -- need to be sent in gluster codebase for creating export configuration file script file(Downstream only) ii.) Entries_HWMark in CACHEINODE{} in ganesha.conf -- current value 25k, need to change atleast to 100K Reason -- it impact performance if the workload has more than 25k entries Patch -- need to modify ganesha.conf next build iii.) Chunks_HWMark in CACHEINODE{} in ganesha.conf -- current value is default 100K, need to reduced to 1000 Reason -- having more value than Entries_HWMark results more caching at dirent cache and if the entry is missed in mdcache then it triggers lookup/getattrs for that entry Patch change in ganesh.conf next build Version-Release number of selected component (if applicable): 3.4 Additional info:
I still disagree with setting Chunks_HWMark as low as 1000.
Jiffin, is there a Doc BZ to document the preferred values for these settings in rhgs-3.4?
Verified this BZ with # rpm -qa | grep ganesha nfs-ganesha-2.7.3-3.el7rhgs.x86_64 glusterfs-ganesha-6.0-3.el7rhgs.x86_64 nfs-ganesha-debuginfo-2.7.3-3.el7rhgs.x86_64 nfs-ganesha-gluster-2.7.3-3.el7rhgs.x86_64 As discussed over IRC,this BZ is validated for only two params 1. Entries_HWMark --> Later was decided to keep this value as 125K instead of 100K 2. Chunks_HWMark Changes made in ganesha.conf for the above 2 params are now in place. ======== CACHEINODE { Entries_HWMark = 125000; Chunk_HWMark = 1000; } ======== "up_poll_usec" related param is not valid for 3.5.0 release. Moving this BZ to verified state.
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, 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/RHEA-2019:3252
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days