Engine: refactor task retry backoff logic #123
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
Signed-off-by: Thomas Schaffer <thomas.schaffer@corp.ovh.com>
Signed-off-by: Thomas Schaffer <thomas.schaffer@corp.ovh.com>
rbeuque74
approved these changes
Apr 9, 2020
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.
Signed-off-by: Thomas Schaffer thomas.schaffer@corp.ovh.com
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Behavior fix
What is the current behavior? (You can also link to an open issue here)
The retry backoff follows a pseudo logarithmic curve.
What is the new behavior (if this is a feature change)?
Each retry pattern is assigned a specialized curve: linear from 1h to 3h (10 mins increments) for hours retry pattern, linear from 1 min to 30 mins (x1.6 coef) for minutes retry pattern, exponential from 10 secs to 10mins (x1.25 factor) for seconds retry pattern.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information: