<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 05/12/2015 02:15 AM, Christopher
Pereira wrote:<br>
</div>
<blockquote cite="mid:555114F2.7040607@imatronix.cl" type="cite">On
11-05-2015 15:40, Christopher Pereira wrote:
<br>
<blockquote type="cite">
<br>
<blockquote type="cite">There is an arbiter feature for replica
3 volumes
(<a class="moz-txt-link-freetext" href="https://github.com/gluster/glusterfs/blob/master/doc/features/afr-arbiter-volumes.md">https://github.com/gluster/glusterfs/blob/master/doc/features/afr-arbiter-volumes.md</a>)
being released in glusterfs 3.7 which would prevent files from
going into split-brains, you could try that out. If the writes
can cause a split-brain, it is failed with an ENOTCONN to the
application.
<br>
</blockquote>
</blockquote>
<br>
Seems to be broken, because files are also stored on the 3rd
brick, even when using "replica 3 arbiter 1".
<br>
Also, I don't see the .meta dir inside the mount point.
<br>
<br>
Bricks 1 and 2 are using:
<br>
<br>
glusterfs-3.7.0beta1-0.131.gitf54b232.el7.centos.x86_64
<br>
glusterfs-rdma-3.7.0beta1-0.131.gitf54b232.el7.centos.x86_64
<br>
glusterfs-cli-3.7.0beta1-0.131.gitf54b232.el7.centos.x86_64
<br>
glusterfs-api-3.7.0beta1-0.131.gitf54b232.el7.centos.x86_64
<br>
glusterfs-server-3.7.0beta1-0.131.gitf54b232.el7.centos.x86_64
<br>
glusterfs-geo-replication-3.7.0beta1-0.131.gitf54b232.el7.centos.x86_64
<br>
glusterfs-libs-3.7.0beta1-0.131.gitf54b232.el7.centos.x86_64
<br>
glusterfs-fuse-3.7.0beta1-0.131.gitf54b232.el7.centos.x86_64
<br>
vdsm-gluster-4.17.0-778.git597bb40.el7.noarch
<br>
glusterfs-debuginfo-3.7.0beta1-0.155.git72f80ae.el7.centos.x86_64
<br>
<br>
Brick 3 is using:
<br>
<br>
glusterfs-fuse-3.8dev-0.58.gitf692757.el7.centos.x86_64
<br>
glusterfs-geo-replication-3.8dev-0.58.gitf692757.el7.centos.x86_64
<br>
glusterfs-cli-3.8dev-0.58.gitf692757.el7.centos.x86_64
<br>
glusterfs-api-3.8dev-0.58.gitf692757.el7.centos.x86_64
<br>
glusterfs-server-3.8dev-0.58.gitf692757.el7.centos.x86_64
<br>
glusterfs-rdma-3.8dev-0.58.gitf692757.el7.centos.x86_64
<br>
vdsm-gluster-4.17.0-743.gite5856da.el7.noarch
<br>
glusterfs-libs-3.8dev-0.58.gitf692757.el7.centos.x86_64
<br>
glusterfs-3.8dev-0.58.gitf692757.el7.centos.x86_64
<br>
glusterfs-debuginfo-3.8dev-0.58.gitf692757.el7.centos.x86_64
<br>
<br>
<br>
</blockquote>
Hi Christopher,<br>
The patches for arbiter logic have gone in for 3.7.0beta2. Could you
upgrade your bricks 1 and 2 to that version or to 3.8dev like brick3
and try? It is recommended to have all 3 nodes on the same version.
After creating the volume, you can check the volfile of the 3rd
brick- it must contain the arbiter xlator in the graph. i.e.
/var/lib/glusterd/vols/<volname>/<volname.IP.the_third_brick.vol
must have this entry:<br>
<br>
<i>volume <volname>-arbiter</i><i><br>
</i><i> type features/arbiter</i><i><br>
</i><i> subvolumes <volname>-posix</i><i><br>
</i><i>end-volume</i><br>
<br>
Thanks,<br>
Ravi<br>
<br>
</body>
</html>