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

Jitter algorithm not random once at maxium delay #8

Closed
fishcakez opened this issue Mar 24, 2015 · 2 comments
Closed

Jitter algorithm not random once at maxium delay #8

fishcakez opened this issue Mar 24, 2015 · 2 comments

Comments

@fishcakez
Copy link
Contributor

Once the maximum delay is reached using the jitter type the delay is always the maximum. This leads to convergence if multiple processes using backoff delay communicate with a bottleneck. Once one processes gets queued behind another at the bottleneck they remain in sync for the next (maximum) backoff delay (and all future maximum delays). Because the grouping remains for future delays the effect snowballs and more processes join the batch leading to a thundering herd.

Obviously the same effect could occur with the normal type but the jitter algorithm should produce random delays to avoid this.

@fishcakez
Copy link
Contributor Author

/cc @jpuigm

@jpuigm
Copy link
Contributor

jpuigm commented Mar 24, 2015

@fishcakez Nice catch, thanks for contributing!

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

Successfully merging a pull request may close this issue.

2 participants