mirror of
https://github.com/versity/scoutfs.git
synced 2026-01-04 03:14:02 +00:00
The default TCP keepalive value is currently 10s, resulting in clients being disconnected after 10 seconds of not replying to a TCP keepalive packet. These keepalive values are reasonable most of the times, but we've seen client disconnects where this timeout has been exceeded, resulting in fencing. The cause for this is unknown at this time, but it is suspected that network intermissions are happening. This change adds a configurable value for this specific client socket timeout. It enforces that its value is above UNRESPONSIVE_PROBES, whose value remains unchanged. The default value of 10000ms (10s) remains the trusted value. It is enirely unclear and untested what values are reasonable and which ones are not. Since the value of this setting can and will interact with other timeout values, care must be taken to not exceed certain other timeout values. I've tested this only briefly with values of 5000 and 25000. Outside that range is likely problematic. Signed-off-by: Auke Kok <auke.kok@versity.com>