-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
session: boostrap delete isolation engines from glo... (#16622) #16802
session: boostrap delete isolation engines from glo... (#16622) #16802
Conversation
Signed-off-by: sre-bot <[email protected]>
/run-all-tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lzmhhh123 please resolve conflicts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests |
@sre-bot merge failed. |
cherry-pick #16622 to release-3.1
What problem does this PR solve?
issue: close #16624
Problem Summary: When tidb-server is upgraded from 3.1-beta to a higher version. There is a
tidb_isolation_read_engines
inmysql.global_variables
. It may lead a wrong behavior such as tidb-dashboard can't read the cluster-info table. So we add a new version for bootstrap to delete it.What is changed and how it works?
How it Works: delete the value in
mysql.global_variables
when tidb-server bootstrap.Related changes
Check List
Tests
Side effects
Release note