Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Adding as an issue as it appears not to have been raised as one before?)
CockroachDB recommend the use of retries should we see a SQL error code 40001, which represents a lock wait timeout. We are adding a pair of classes:
DefaultExecutionStrategy
CockroachDBRetryingStrategy
This should be straightforward to extend if other databases need a similar approach (or if people want to fork and try their own strategies).
The text was updated successfully, but these errors were encountered:
#2663 Add retrying pattern for CockroachDB
53a90f1
Released in 6.2.2
Sorry, something went wrong.
No branches or pull requests
(Adding as an issue as it appears not to have been raised as one before?)
CockroachDB recommend the use of retries should we see a SQL error code 40001, which represents a lock wait timeout. We are adding a pair of classes:
DefaultExecutionStrategy
- which simply fires a SQL call at the db onceCockroachDBRetryingStrategy
- which attempts retries up to a set limit if the above code is received from the database.This should be straightforward to extend if other databases need a similar approach (or if people want to fork and try their own strategies).
The text was updated successfully, but these errors were encountered: