Retry Mechanism for Deployment Requests #193
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
movchan74
added
enhancement
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.
Summary:
This PR implements retry logic to ensure deployment requests are retried upon failure, addressing the issue of one-time request attempts that do not retry on failure.
Key Changes:
Retry Logic Added to Deployment Requests: Introduced a retry mechanism with configurable parameters such as the number of retries, delay between retries, and specific exceptions that can trigger a retry.
Exponential Backoff with Jitter: Integrated
sleep_exponential_backofffor delays between retries, applying full jitter to reduce the chances of synchronized retry requests.Tests for Retry Mechanism: Added unit tests to validate the retry functionality.