Gluster users - Jan 2017 - gluster native client failover testing

Hi all

As the subject states, I'm doing glusterfs native client testing.

I've configured two test gluster servers (RHEL7) running glusterfs 3.7.18.

My test client is RHEL5.11 with the glusterfs-fuse RPM 3.7.18 installed.

The client has the following in /etc/fstab:
devfil01:/gv0   /share   glusterfs
 defaults,backupvolfile-server=devfil02   0 0

I used the following shell snippet to test gluster native client failover:
for I in `seq -w 1 1000`; do sleep 0.05; touch /share/test$I; echo $I; done

A hundred or so iterations in, I rebooted devfil01.  The snippet stopped
while devfil01 was down.  It didn't swap over to devfil02.

I've manually tested that devfil02 is working.

Any ideas what I'm doing wrong?

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20170105/6e8e4469/attachment.html>

> I've configured two test gluster servers (RHEL7) running glusterfs
3.7.18.
> [...] 
> Any ideas what I'm doing wrong?
I'd say you need 3 servers. GlusterFS goes RO without a quorum, and one
server
isn't a quorum. That's to avoid split brains.

-- 
Kevin Lemonnier
PGP Fingerprint : 89A5 2283 04A0 E6E9 0111
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Digital signature
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20170105/9078fb69/attachment.sig>