Periodic reconnect to avoid stale UDP connections #51
+118
−45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jonnymcc
force-pushed
the
periodic-reonnect
branch
from
d2d0c87
to
3a46488
Compare
added 6 commits
April 4, 2018 14:43
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Allows the client to periodically reconnect to the server.
Why?
We are using this library within Kubernetes and when our statsd servers get recreated (within Kubernetes) a connection to an old service endpoint results in metrics being emitted via UDP and going nowhere. We believe this is due to conntrack keeping the route open because there is at least one client that is connected to it (the app that implements this library).