-
Notifications
You must be signed in to change notification settings - Fork 131
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
skip wrongly write ActionUpdateTiFlashReplicaStatus job #947
Conversation
/run-all-tests tidb=release-4.0 tikv=release-4.0 pd=release-4.0 |
/run-all-tests tidb=release-4.0 tikv=release-4.0 pd=release-4.0 |
/run-all-tests tidb=release-4.0 tikv=release-4.0 pd=release-4.0 |
/run-unit-test |
/run-all-tests tidb=release-4.0 tikv=release-4.0 pd=release-4.0 |
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
cherry pick to release-3.1 in PR #948 |
What problem does this PR solve?
ref #941
What is changed and how it works?
skip wrongly write ActionUpdateTiFlashReplicaStatus job
after pingcap/tidb#16049 there's no any ActionUpdateTiFlashReplicaStatus job that will be written.
Check List
Tests
create table t(id int);
ALTER TABLE t SET TIFLASH REPLICA 3 LOCATION LABELS "rack", "host", "abc"; // model.ActionSetTiFlashReplica
curl -X POST -d '{"id":45,"region_count":3,"flash_region_count":3}' https://127.0.0.1:10080/tiflash/replica // model.ActionUpdateTiFlashReplicaStatus
performance write on table t and check can still replicate. - No code
Code changes
Side effects
Related changes