24-1: Cleanup persistent locks on table rename - #4979
Merged
snaury merged 1 commit intoJun 3, 2024
Conversation
Contributor
Contributor
|
⚪
|
snaury
marked this pull request as ready for review
June 3, 2024 09:04
snaury
changed the title
snaury
enabled auto-merge (squash)
June 3, 2024 09:06
fomichev3000
approved these changes
Jun 3, 2024
This was referenced Jun 7, 2024
Closed
Closed
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
2 participants
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.
Changelog entry
Cleanup persistent locks on table rename.
Changelog category
Additional information
Uncommitted changes may have lingered after a table is renamed. In the worst case persistent locks could become resurrected after a shard is restarted, causing an invariant assertion during a commit attempt.
Fixes #4782.
Merges #4962.