[Gluster-devel] Client hang on HA config when restoring a server

Anand Avati avati at zresearch.com
Thu Aug 9 09:51:39 UTC 2007

  Please upgrade to patch-445. This bug is fixed in that patch.


2007/8/9, Kevan Benson <kbenson at a-1networks.com>:
> Same config from previous post:
> System configs at http://glusterfs.pastebin.com/m52564c56
> Server A:
> Server B:
> Client A:
> Client B:
> I have noticed in this config thought that sometimes on restoring a
> failed server, one of the clients will not by able to list the mount still
> (reports error "ls: /mnt/glusterfs/: Transport endpoint is not
> connected") until I restart the client on that system.  In this case,
> the system goes from both clients working with one failed server to
> one client NOT working with both servers up.  The client fails at the
> point that the active server reconnects to the inactive server.
> The last thing the client log shows is this:
> 2007-08-08 12:25:24 D [client-protocol.c:4218:client_protocol_reconnect]
> share: breaking reconnect chain
> And the server log (on the only server showing activity when request
> is made) shows this for every ls request:
> 2007-08-08 12:27:11 E [unify.c:337:unify_lookup] share: : Argument not
> right
> As stated above, restarting the client fixes this problem.  The other
> client in this setup has not problem, but it's random (to me at least)
> which client has the problem.
> --
> - Kevan Benson
> - A-1 Networks
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> http://lists.nongnu.org/mailman/listinfo/gluster-devel

It always takes longer than you expect, even when you take into account
Hofstadter's Law.

-- Hofstadter's Law

More information about the Gluster-devel mailing list