Red Hat Bugzilla – Bug 1306667
Newly created volume start, starting the bricks when server quorum not met
Last modified: 2016-09-17 12:45:22 EDT
Description of problem:
Had a four node cluster and created a Distributed volume using one brick and enabled the server quorum and server-quorum ratio was 90, and stopped glusterd in one of the node to achieve server quorum not met condition based on server quorum ratio set and started the volume, *it's started and bricks are online**
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Have 4 node cluster (node-1..4)
2.Create a simple distributed volume using one brick
3.Enabled the server quorum
4.Set the server quorum ration to 90
5.Stop glusterd on one of the node (eg :node-4)
6.Try to start the volume now //will start and bricks will be online
Bricks are online when server quorum not met
Bricks should be in offline when server quorum not met
Could you please check this issue?
This looks like a regression caused by http://review.gluster.org/12718
Marking this bug as Regression failed based on above details
upstream patch for this bug available: http://review.gluster.org/13442
We have a crude workaround here which is as follows:
1. Disable server side quorum by gluster volume reset <volname> cluster.server-quorum-type
2. Stop the volume
3. Turn on server side quorum by gluster volume set <volname> cluster.server-quorum-type server
The fix is now available in rhgs-3.1.3 branch, hence moving the state to Modified.
Verified this bug using the build "glusterfs-3.7.9-1"
Repeated the reproducing steps mentioned in description section of bug, Fix is working properly, volume start is not happening when "server side quorum not met"
Moving to verified state based on above info.
This bug doesn't need a doc text since its a regression. Apologies for this effort waste.
Also if you see any bugs which Gaurav has worked on, raise needinfo on me instead of Satish :)
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.