Description of problem: When the Glusterd is connected to less than half of the number of members in cluster, glusterd will kill the local bricks of the volumes on which the server side quorum is enabled. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Normally a new feature would have low severity, but the lack of this affects so many users that I'm bumping it up by two.
CHANGE: http://review.gluster.org/4162 (libglusterfs: Implement float percentage) merged in master by Vijay Bellur (vbellur)
CHANGE: http://review.gluster.org/3811 (mgmt/glusterd: Implementation of server-side quorum) merged in master by Vijay Bellur (vbellur)
CHANGE: http://review.gluster.org/4228 (tests: Add volume utils in a new file) merged in master by Vijay Bellur (vbellur)
CHANGE: http://review.gluster.org/4229 (tests: Add volume set tests for quorum) merged in master by Vijay Bellur (vbellur)
CHANGE: http://review.gluster.org/4291 (glusterd: Set op-version for quorum options) merged in master by Anand Avati (avati)
hi did someone verify that it really helps with the split-brains? thanks.
Ah(In reply to Aharon Canan from comment #7) > hi > > did someone verify that it really helps with the split-brains? > > thanks. Yes, it does so. I tested that with Red Hat Storage. You can read more about this feature here : http://www.gluster.org/community/documentation/index.php/Features/Server-quorum