Description of problem: Enable brick multiplexing in rhgs container which enables high number of volume support in glusterd. Test that 600 - 700 PVs (a mix of RWM + RWO) can be created per cluster with the RHGS 3.3 container because of resource consumption improvements enabled by brick multiplexing. The nodes must have adequate resource for the RHGS container. The main feature that enables this capability will be delivered by the RHGS 3.3 release. Version-Release number of selected component (if applicable): rhgs-server-docker How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
brick multiplexing is enabled by default in cns 3.6 builds. Verified in build - cns-deploy-5.0.0-34.el7rhgs.x86_64 Volume Name: vol_ef52877282c87107c1d81305f2b89628 Type: Replicate Volume ID: 23e9abee-06a8-4336-9549-ee27e3cc040c Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: 10.70.46.11:/var/lib/heketi/mounts/vg_d3034957f7e4210e4114d35db11eb357/brick_e4267465d0d35f7219f91739ba74d4de/brick Brick2: 10.70.47.69:/var/lib/heketi/mounts/vg_ccb71b49c7dd9ea0137da0c1eac7d8b4/brick_69e3fecfbf0ab87efd86031a90e54317/brick Brick3: 10.70.47.23:/var/lib/heketi/mounts/vg_5aeadbb32893003a2928fb86e285bd29/brick_030621672f87163ecfe988c25aede043/brick Options Reconfigured: transport.address-family: inet nfs.disable: on cluster.brick-multiplex: on Moving the bug to verified.
doc text looks good to me
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-2017:2877