search for: tcp_usertimeout

...VM running the brick - physically pulling out the network cable Basically all those different scenarios where TCP/IP doesn't get a chance to inform the other end that it is going down. Note that some of the scenarios of ungraceful network shutdown can be identified using TCP_KEEPALIVE and TCP_USERTIMEOUT [1]. However, at the time when heartbeat mechanism was introduced in Glusterfs, TCP_KEEPALIVE couldn't identify all the ungraceful network shutdown scenarios and TCP_USER_TIMEOUT was yet to be implemented in Linux kernel. One scenario which TCP_KEEPALIVE could identify was the exact scenario TC...

...physically pulling out the network cable > Basically all those different scenarios where TCP/IP doesn't get a chance > to inform the other end that it is going down. Note that some of the > scenarios of ungraceful network shutdown can be identified using > TCP_KEEPALIVE and TCP_USERTIMEOUT [1]. However, at the time when heartbeat > mechanism was introduced in Glusterfs, TCP_KEEPALIVE couldn't identify all > the ungraceful network shutdown scenarios and TCP_USER_TIMEOUT was yet to > be implemented in Linux kernel. One scenario which TCP_KEEPALIVE could s/could/coul...

Hi, I have a question regarding the "ping-timeout" option. I have been researching its purpose for a few days and it is not completely clear to me. Especially that it is apparently strongly encouraged by the Gluster community not to change or at least decrease this value! Assuming that I set ping-timeout to 10 seconds (instead of the default 42) this would mean that if I have a network