[Bugs] [Bug 1511698] New: Enabling Halo sets volume to Read Only

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1511698

            Bug ID: 1511698
           Summary: Enabling Halo sets volume to Read Only
           Product: GlusterFS
           Version: 3.12
         Component: replicate
          Assignee: bugs at gluster.org
          Reporter: jcope at redhat.com
                CC: bugs at gluster.org



Description of problem:

In GCE, I have 4 instances, each with one 10gb brick. 2 instances are in the US
and the other 2 are in Asia (with the hope that it will drive up i/o latency
sufficiently). The bricks make up a Replica-4 volume. Before I enable halo, I
can mount the volume and r/w files.

However, when I set `cluster.halo-enabled yes`, I can no longer write to the
volume: 

[root at jcope-rhs-g2fn vol]# touch /mnt/vol/test1 
touch: setting times of ‘test1’: Read-only file system.

Thanks to a helpful user on the mailing list, setting these volume values
solves the issue:

cluster.quorum-type fixed 
cluster.quorum-count 2

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

glusterfs-client-xlators-3.12.1-2.el7.x86_64
glusterfs-libs-3.12.1-2.el7.x86_64
glusterfs-api-3.12.1-2.el7.x86_64
glusterfs-server-3.12.1-2.el7.x86_64
glusterfs-3.12.1-2.el7.x86_64
glusterfs-cli-3.12.1-2.el7.x86_64
glusterfs-fuse-3.12.1-2.el7.x86_64

How reproducible:

100%

Steps to Reproduce:
1.  Setup a replica volume.
2.  Enable halo (gluster volume set gv0 cluster.halo-enabled yes)
3.  Write to the volume.

Actual results:
touch: setting times of ‘test1’: Read-only file system 

Expected results:
File written to volume

Additional info:

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