Client-side restart of failed transactions on CockroachDB #22240
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
🦋 Changeset detectedLatest commit: 827439f The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
paescuj
requested review from
a team,
DanielBiegler and
licitdev
and removed request for
a team
hanneskuettner
requested changes
Apr 25, 2024
Co-authored-by: Hannes Küttner <[email protected]>
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.
Scope
Implement client-side restart of failed transactions on CockroachDB.
On failed transactions due to serialization error (another transaction attempting to write to the same data), CockroachDB responds with a
40001error code 1, which indicates that the transaction should be restarted on client-side. This is usually enough to ensure that the transaction can still be executed successfully, as it is now carried out against the latest applicable state.Reproduction
Before
Notice the missing relation on the
user_updatedfieldbefore.mp4
After
after.mp4
Potential Risks / Drawbacks
Review Notes / Questions
None
Fixes #21424 (2/2, as follow-up on #22023)
Footnotes
https://www.cockroachlabs.com/docs/stable/transaction-retry-error-reference ↩