[improvement] : use fixed retryAfter instead of exponential backoff #576
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 this PR does / why we need it:
We would like to use fixed backoff than exponential as exponential starts with microseconds and makes 10+ requests before it reaches 10 sec or higher backoff time. Since POST calls to /v4/linode/instances have low limits, we would like to make sure we don't make too many POST calls in case of an error due to exponential backoff. With this fix, we are now retrying at a fixed interval. This also affects other calls which use the same method to calculate how soon it should retry, but having a fixed interval for them is also fine.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
TODOs: