Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection watchdog #62

Open
liveforeverx opened this issue Aug 21, 2015 · 3 comments
Open

Connection watchdog #62

liveforeverx opened this issue Aug 21, 2015 · 3 comments
Assignees

Comments

@liveforeverx
Copy link
Contributor

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

@surik
Copy link
Contributor

surik commented Aug 27, 2015

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

@thz
Copy link
Contributor

thz commented Aug 27, 2015

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
Copy link
Member

hwinkel commented Aug 30, 2015

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants