On 04/07/2015 04:15 AM, CJ Baar wrote:
I am hoping someone can give me some direction on this. I have been searching
and trying various tweaks all day. I am trying to setup a two-node cluster with
a replicated volume. Each node has a brick under /export, and a local mount
using glusterfs under /mnt.
gluster volume create test1 rep 2 g01.x.local:/exports/sdb1/brick
g02.x.local:/exports/sdb1/brick
gluster volume start test1
mount -t glusterfs g01.x.local:/test1 /mnt/test1
When I write a file to one node, it shows up instantly on the other… just as I
expect it to. The volume was created as:
My problem is that if I reboot one node, the mount on the other completely
hangs until the rebooted node comes back up. This seems to defeat the purpose
of being highly-available. Is there some setting I am missing? How do I keep
the volume on a single node alive during a failure?
Any info is appreciated. Thank you.
You can explore the network.ping-timeout setting; try reducing it from
the default value of 42 seconds.
-Ravi
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
