Description of problem: ----------------------- server-quorum when not met kills the brick process on that node. This affects the data path. It would be useful to provide the flexibility to choose the behavior of **not** killing the bricks under the circumstance of server-quorum not met scenario. Version-Release number of selected component (if applicable): ------------------------------------------------------------- mainline How reproducible: ----------------- Not Applicable for feature enhancement Steps to Reproduce: ------------------- Not applicable for feature enhancement Actual results: --------------- Bricks are killed when server-quorum not met Expected results: ----------------- Provide the flexibility to opt for **not** killing the bricks, when server-quorum is not met Additional info: ---------------- The motivation for this bug resulted from the gluster user who has complained about data-path that is affected as result of loss of 2 nodes in a 4 node cluster. In this case, all the virtual machines running on the gluster volume got paused.
Migrated to github: https://github.com/gluster/glusterfs/issues/582 Please follow the github issue for further updates on this bug.