Repository navigation
storage: Avoid nested transactions during snapshot record recovery - #4165
Merged
Merged
Conversation
Signed-off-by: Jason Overmier <jason.r.overmier@gmail.com>
This file contains hidden or 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.
Finish the local-instance listing transaction before repairing snapshot volume records. Repair opens additional cluster transactions, so keeping the listing transaction open makes it wait for the database connection until the outer transaction times out.
Add a native database test covering missing-record repair, existing snapshot metadata, and idempotence. Two repair calls took 60.20 seconds on main and 0.19 seconds with the fix.
Validation: full Go suite, all 17 static-analysis recipe checks, and daemon/CLI builds passed. The repository's nonfatal govulncheck still reports existing dependency findings.