One node goes offline, the other node can't see the replicated volume anymore

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

 



Oh yes ? telnet localhost 24007 was successful on both nodes even after isolating fw1.


-          Greg

From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Greg Scott
Sent: Saturday, July 13, 2013 6:58 PM
To: 'Joe Julian'; 'gluster-users at gluster.org'
Subject: Re: One node goes offline, the other node can't see the replicated volume anymore

Log files sent privately to Joe.  If others from the community want to look at them, I?m OK with posting them here.  I don?t think they have anything confidential.  Now that I know about that 42 second timeout, the behavior makes more sense.   Why 42?   What?s special about 42?   Is there a way I adjust that down for my application to, say, 1 or 2  seconds?


-          Greg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130714/74d007da/attachment.html>


[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