Added request retry mechanism #308
Merged
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.
Fix intermittent connection issue
ConnectionErrorexceptions at the application layer, which ensures retries even when there’s no response from the server.intermittent connection issue
a. Number of times to retry:
Default: 5 retries (defined in DEFAULTS['max_retries'])
Configurable via constructor parameter
Uses exponential backoff with jitter
Default parameters:
Initial delay: 1 second
Max delay cap: 60 seconds
Formula: Each retry doubles the previous delay (delay_seconds *= 2), with added random jitter.
Jitter is calculated as:
jitter_value = random.uniform(-self.jitter, self.jitter)Final delay is:
delay_seconds * (1 + jitter_value), capped at max_delayc. Specific conditions to retry on:
retries on:
requests.exceptions.ConnectionError: Network connectivity issuesrequests.exceptions.Timeout: Request timeout errorsdoes NOT retry on:
requests.exceptions.RequestException: Other request exceptions (edited)