[Gluster-devel] ping timeout

[Stephan von Krawczynski]

Hi Christopher,

I advise you to really try the most important part of your description you
take for granted - the reconnect case.
Our experiences are quite away from what you think is the worst case. You can
easily check out what happens if you just pull the network cable 5 times in 10
minutes. We came to the conclusion that disconnect/reconnect should be avoided
under all circumstances. Interestingly stopping one servers' glusterfsd and
restarting it works out quite well in our setup. So offline-updating a server
(which was our main purpose) is quite ok.

-- 
Regards,
Stephan



On Thu, 18 Mar 2010 08:33:51 -0400 (EDT)
Christopher Hawkins <chawkins at bplinux.com> wrote:

> I have a question re: ping timeout for any of the dev's. The minimum value is 5 and the max is 1013... But in my case, I use replicate to mirror server pairs that are each gigabit connected by crossover cables. The latency is very low. 5 seconds is a long time and personally I would like them to give up on the failed link after 500ms or so, so the mountpoint becomes available quickly to the remaining node. 
> 
> Or I would at least like to test it and see if it's stable that way; I don't mind getting disconnected early in the case of a slow server, because it will just reconnect when the server comes back. Is there any hope for being able to tweak this parameter? Or is there a reason why it simply cannot be lower than 5?
> 
> Thanks for any insight and for glusterfs!
> 
> Christopher Hawkins
> 
> 
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>