release-20.1: backupccl: handle retry errors during system table restoration #50004
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
Previously, if the transaction which restored the system table data returned a retry exception, the job would fail and the entire restore would need to be restarted. This change automatically retries restoring the system table data. Release note (enterprise change): Full cluster restore is now more resilient to transient transaction retry errors while it restores.
|
This change is |
dt
approved these changes
Jun 11, 2020
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.
Backport 1/1 commits from #49950.
/cc @cockroachdb/release
Previously, if the transaction which restored the system table data
returned a retry exception, the job would fail and the entire restore
would need to be restarted. This change automatically retries restoring
the system table data.
Release note (enterprise change): Full cluster restore is now more
resilient to transient transaction retry errors while it restores.