[Bugs] [Bug 1313017] New: Quorum is not met and writes are restricted with quorum-type auto in a 3 node system

bugzilla at redhat.com bugzilla at redhat.com
Mon Feb 29 18:02:21 UTC 2016


            Bug ID: 1313017
           Summary: Quorum is not met and writes are restricted with
                    quorum-type auto in a 3 node system
           Product: GlusterFS
           Version: 3.7.6
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: cpetersen4 at gmail.com
                CC: bugs at gluster.org

Description of problem:
My cluster has 3 replicated nodes and was set to quorum-type auto.  I am using
nfs-ganesha to share via NFS 3 to an ESXi cluster for shared VM storage.  I
initiated a test failure to one of the bricks.  The nfs-ganesha gluster client
log stated that writes were not allowed as quorum had not been met.

After switching to quorum-type fixed and quorum count of 2, the problem still
remained.  It was only after switching to an undesirable quorum-count of 1 that
writes were allowed again.

I tore down the entire cluster and recreated it.  This time I started out with
the quorum-type set to fixed and the quorum-count set to 2.  I initiated
another test failure to one of the bricks and was able to keep writing to the
cluster properly.

Version-Release number of selected component (if applicable):
nfs-ganesha 3.7.6

How reproducible:
This happened twice through troubleshooting as I tore down and recreated the
cluster.  I have not confirmed how reproducible this is intentionally.

Steps to Reproduce:
1.  Create replicated 3 node cluster
2.  Set quorum-type to auto
3.  Halt one of the bricks and test writing to the cluster

Actual results:
Quorum is broken when one brick out of 3 is lost

Expected results:
Quorum should be maintained as 2 of 3 bricks are still alive

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list