Add static retry strategy #4393
Draft
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.
Motivation and Context
This implementation offers a simpler alternative to the adaptive retry strategy for use cases where static rate limiting is preferred. The strategy uses a token bucket for rate limiting combined with exponential backoff, but maintains fixed token bucket parameters rather than dynamically adjusting rates based on service responses.
Description
This PR adds a new StaticRetryStrategy that provides retry logic with token bucket rate limiting and exponential backoff, without the dynamic rate calculation used in the standard retry strategy.
I am still working on getting the test-util tests correct and passing, but wanted to get input on the general implementation of the PR sooner rather than later.
Testing
Ran cargo test using the instructions outlined in the README:
Checklist
.changelogdirectory, specifying "client," "server," or both in theapplies_tokey.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.