ddl: fix parallel execution of "drop DB" and other DDL issue (#17566) #17657
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
Signed-off-by: sre-bot <[email protected]>
|
/run-all-tests |
sre-bot
added
sig/sql-infra
AilinKid
approved these changes
Jun 4, 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.
cherry-pick #17566 to release-3.0
What problem does this PR solve?
Issue Number: close #17565
Problem Summary:
Parallel execution of "drop database" and other DDL (such as "alter database") may cause panic.
Because we don't check the return value in
GetDatabasein the background.What is changed and how it works?
What's Changed:
How it Works:
After executing
GetDatabase, we need to check whether the return value is nil.Related changes
Check List
Tests
Side effects
Release note