[Gluster-users] Exact purpose of network.ping-timeout

Omar Kohl omar.kohl at iternity.com
Thu Dec 21 17:14:14 UTC 2017


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 outage of 11 seconds then Gluster internally would have to re-allocate some resources that it freed after the 10 seconds, correct? But apart from that there are no negative implications, are there? For instance if I'm copying files during the network outage then those files will continue copying after those 11 seconds.

This means that the only purpose of ping-timeout is to save those extra resources that are used by "short" network outages. Is that correct?

If I am confident that my network will not have many 11 second outages and if they do occur I am willing to incur those extra costs due to resource allocation is there any reason not to set ping-timeout to 10 seconds?

The problem I have with a long ping-timeout is that the Windows Samba Client disconnects after 25 seconds. So if one of the nodes of a Gluster cluster shuts down ungracefully then the Samba Client disconnects and the file that was being copied is incomplete on the server. These "costs" seem to be much higher than the potential costs of those Gluster resource re-allocations. But it is hard to estimate because there is not clear documentation what exactly those Gluster costs are.

In general I would be very interested in a comprehensive explanation of ping-timeout and the up- and downsides of setting high or low values for it.

Kinds regards,
Omar


More information about the Gluster-users mailing list