Description of problem: Currently, in a multi-clustered nfs-ganesha environment, to keep ganesha md-cache of all the servers in sync, we spawn a new thread (fsal_up) for each volume exported which continuously polls for any upcalls sent by backend glusterfs server. These threads are not effective and may end up consuming lot of CPU depending on no. of volumes exported. But with bug1482909, if we decide to use gluserfs md-cache instead of ganesha md-cache, we no longer need upcall threads. This bug to make those threads configurable so that they can be disabled when needed. Few things to note: 1) This new option shall be part of FSAL {name = Gluster } block. 2) In case if there are multiple shares exporting sub-dir of the same volume and even if one of those export block has this option turned on, upcall thread shall be spawned for that volume. 3) any change in value of this new option shall require re-export of the shares(/volume). Version-Release number of selected component (if applicable): 3.3 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Bug1497139 is filed to track changes needed in gluster sources .
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