search

travelping / hello

Erlang RPC server framework
MIT License
31 stars 20 forks source link

Connection `watchdog` #62

Open liveforeverx opened 9 years ago

liveforeverx commented 9 years ago

If no PONG answer to PING, the error should be written and connection should reconnect.

surik commented 9 years ago

I think for a moment why we don't use TCP keep-alive?

thz commented 9 years ago

no objections to tcp-keep-alive, but it is out-of-scope here. the watchdog has to do a higher level functional check and (more or less brutally) restart the connection (or even the full application).

using tcp-keep-alive to prevent that the watchdog will ever bark is okay (but out of scope here).

hwinkel commented 9 years ago

should we consider ongoing communication as watchdog reset. I.e. CAPWAP Echorequests are not used if there is ongoing communication between the nodes. Or do we this as optimisation.

What are the defaults for watch dog? How often send? How many PONG are allowed to fail, is the good and failure sate known to the application? how ist the sate reported? ist there a defined (log) message if watchdog fails?