[db-wg] NRTM replication inefficiencies

Hi Agoston,

> On 8 Dec 2017, at 15:05, Edward Shryane via db-wg <db-wg at ripe.net> wrote:
> 
> Hi Agoston,
> 
>> On 8 Dec 2017, at 13:43, Horváth Ágoston János via db-wg <db-wg at ripe.net> wrote:
>> 
>> Or you could use TCP's built-in keepalive feature:
>> 
>> http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html
>> 
> 
> Yes, this is already possible, you can set the SO_KEEPALIVE option on the socket.
> 
> However, at least on CentOS7 (Linux), the default is to wait 2 hours before sending a keepalive probe, then 9 probes have to fail (each 75s apart) before declaring the connection is broken. Changing this default behaviour is applied system-wide.
> 
> Adding a protocol-specific keepalive mechanism may still be useful.
> 
> Regards
> Ed
> 

to clarify my earlier reply - changing these system-wide defaults can also be changed on a per-socket basis. 

A client could use the TCP keep alive mechanism, or we could add a periodic keepalive comment on the server side.

Regards
Ed