Transient error bugfix #138
Open
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
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.
Heyo,
as mentioned in Issue #135 the provider was unable to retry transient errors like a paused/resuming DB. This PR enables the provider to retry such errors. I've wrapped all calls that will trigger a query with a retry mechanism. This mechanism checks if the returned error from that call is a transient one. If so, the provider will query the DB again with a fibonacci backoff strategy for a maximum of 100 seconds. If it still fails, the err will be returned the same way as it was returned before the PR. All wrapped funcs should behave as before except the mentioned retry mechanism.