Handling a fuse mount with a failed gluster node

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I am testing out several failure scenarios with GlusterFS.  I have a 3 node replicated gluster that i am testing with.

One test i am having trouble solving is when a host dies.  (i.e. as if someone pulled the power cord out).
- Firewall off a host from the rest of the cluster
- Test time it takes for a fuse mount to respond once the iptables rule is added

With the default settings, the mount hangs for 39 seconds.  If i change ping-timeout to 5 then the mount only hangs for 9.3 seconds.  Is there anyway to eliminate or get the hang time to a negligible value (less than 1 second)?

I have not seem much about handling GlusterFS failure scenarios with my Googling around.

Several blog posts i have looked at:
http://thornelabs.net/2015/02/24/change-gluster-volume-connection-timeout-for-glusterfs-native-client.html
https://joejulian.name/blog/keeping-your-vms-from-going-read-only-when-encountering-a-ping-timeout-in-glusterfs/

Thanks,
Grant
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux