Description of problem: ======================= Had a four node cluster, created and started a replica volume (1*2 ) and enabled the server quorum and server-quorum ratio was set to 90, and stopped glusterd in one of the node to achieve server quorum not met condition based on server quorum ratio set and tried to replace one of the brick, it's failed with error message "volume replace-brick: failed: Commit failed on <host>" Version-Release number of selected component (if applicable): ============================================================== glusterfs-3.7.5-19.el7rhgs. How reproducible: ================== Every time Steps to Reproduce: =================== 1.Have 4 nodes (node-1..4) 2.Create a replica volume (1*2) and start it. 3.Enable the server side quorum for the volume 4.Set the server side quorum ratio to 90 5.Stop glusterd in one of the node (eg : node-4) 6.Now check the volume status //bricks will be in offline state 7. Try to replace one of the brick with new brick //it will fail with error message "Commit failed" Actual results: =============== Getting commit failed error message when tried to replace a brick when server quorum not met Expected results: ================= Commit failed error message should not come. Additional info:
Addition info: ============== This issue is with replica volume type.
Assigning it to Anuradha since she mostly work in add/remove/replace brick work flows.
This issue is there from long time with replica volume type.