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... 😎
Diego
On Sep 8, 2017 6:50 AM, "Pavel Szalbot" <pavel.szalbot@xxxxxxxxx> wrote:
On Fri, Sep 8, 2017 at 12:48 PM, Gandalf Corvotempesta
<gandalf.corvotempesta@gmail.com > wrote:
> I think this should be considered a bug
> If you have a server crash, glusterfsd process obviously doesn't exit
> properly and thus this could least to IO stop ?
I agree with you completely in this.
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
