Jitter for manager heartbeats and updates #889
Merged
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
bennybp
changed the title
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.
Description
Adds options for adding jitter to manager heartbeats and updates. This does two things - helps with some random errors related to TCP keepalive, and also prevents the thundering herd effect where lots of managers started at the same time will all try heartbeat/update at the same time as well.
In addition, this PR disables keepalive connections for certain manager requests that are expected to be infrequent.
Heartbeat frequency jitter is controlled by the server, while update frequency jitter is set in the manager config.
Changes in this PR are backwards & forwards compatible.
Status