Description of problem: ------------------------ gluster v set help shows no description for the Brick MUXing tunable : [root@gqas013 ~]# gluster v set help|grep cluster.brick-multiplex [root@gqas013 ~]# [root@gqas013 ~]# gluster v set help|grep cluster.brick [root@gqas013 ~]# Version-Release number of selected component (if applicable): ------------------------------------------------------------- glusterfs-3.8.4-23.el7rhgs.x86_64 How reproducible: ----------------- Always.
Proposing as a blocker for RHGS 3.3.0 post discussion with Atin.
upstream patch : https://review.gluster.org/#/c/17790
Downstream patch: https://code.engineering.redhat.com/gerrit/112820
Verified on glusterfs-3.8.4-35. [root@gqas003 ~]# gluster v set help|grep "cluster.brick" Option: cluster.brick-multiplex [root@gqas003 ~]# [root@gqas003 ~]# gluster v set help|grep "multiplex" Option: cluster.brick-multiplex Option: cluster.max-bricks-per-process Default Value: 0 Description: This option can be used to limit the number of brick instances per brick process when brick-multiplexing is enabled. If not explicitly set, this tunable is set to 0 which denotes that brick-multiplexing can happen without any limit on the number of bricks per process. Also this option can't be set when the brick-multiplexing feature is disabled. Option: cluster.brick-multiplex Default Value: off Description: This global option can be used to enable/disable brick multiplexing. Brick multiplexing ensures that compatible brick instances can share one single brick process.
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/RHBA-2017:2774