<div dir="auto">I would prefer the behavior was different to what it is of I/O stopping. The argument I heard for the long 42 second time out was that MTBF on a server was high, and that the client reconnection operation was *costly*. Those were arguments to *not* change the ping timeout value down from 42 seconds. I think it was mentioned that low ping timeout settings could lead to high cpu loads with many clients trying to reconnect if a short timeout was set. This is all hearsay, so the experts should explain it better... 😎<div dir="auto"><br></div><div dir="auto">Diego</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sep 8, 2017 6:50 AM, "Pavel Szalbot" <<a href="mailto:pavel.szalbot@gmail.com">pavel.szalbot@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Sep 8, 2017 at 12:48 PM, Gandalf Corvotempesta<br>
<<a href="mailto:gandalf.corvotempesta@gmail.com">gandalf.corvotempesta@gmail.<wbr>com</a>> wrote:<br>
> I think this should be considered a bug<br>
> If you have a server crash, glusterfsd process obviously doesn't exit<br>
> properly and thus this could least to IO stop ?<br>
<br>
I agree with you completely in this.<br>
</blockquote></div></div>