<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
we've successfully configured GlusterFS mirroring across two
identical nodes [1].<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<br>
We're running the file share under a Virtual IP address using UCarp.<br>
We have different clients connected using NFS, CIFS and GlusterFS.<br>
<br>
When we simulate a node failure, by unplugging it, it takes about 5
seconds for the CIFS and GlusterFS clients to refresh the connection
and continue operation. The NFS client goes stale. Any connection
(like an ongoing copy) with any client breaks and have to be started
over.<br>
<br>
The connection break behavior is to be expected - the TCP connection
doesn't handle the switch of host. I didn't expect the NFS client to
go stale.<br>
<br>
Will this behavior be any different with four nodes [2]?<br>
Or is there something else I should consider to help the situation?<br>
<br>
[1] <a
href="http://www.howtoforge.com/high-availability-storage-with-glusterfs-3.2.x-on-ubuntu-12.04-automatic-file-replication-across-two-storage-servers">http://www.howtoforge.com/high-availability-storage-with-glusterfs-3.2.x-on-ubuntu-12.04-automatic-file-replication-across-two-storage-servers</a><br>
[2] <a
href="http://www.misdivision.com/blog/setting-up-a-highly-available-storage-cluster-using-glusterfs-and-ucarp">http://www.misdivision.com/blog/setting-up-a-highly-available-storage-cluster-using-glusterfs-and-ucarp</a><br>
<br>
Thank you for your help.<br>
<br>
--<br>
Best Regards<br>
Runar Ingebrigtsen<br>
</body>
</html>