We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the case of many jobs getting enqueued at about the same time, they might overwhelm the system, fail and be retried at some later point.
However if there's so many and they all get retried at the same (exponential backoff) interval, they might still end up causing trouble.
Adding a(n option to add a) random jitter to the retry interval might distribute the load a bit better and resolve the retry stampede.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In the case of many jobs getting enqueued at about the same time, they might overwhelm the system, fail and be retried at some later point.
However if there's so many and they all get retried at the same (exponential backoff) interval, they might still end up causing trouble.
Adding a(n option to add a) random jitter to the retry interval might distribute the load a bit better and resolve the retry stampede.
The text was updated successfully, but these errors were encountered: