-
Notifications
You must be signed in to change notification settings - Fork 500
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
failover for tiflash (#2249) #2269
failover for tiflash (#2249) #2269
Conversation
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-e2e-tests |
/run-all-tests |
@sre-bot merge failed. |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
/run-all-tests |
/run-all-tests |
@sre-bot merge failed. |
/merge |
/run-all-tests |
@sre-bot merge failed. |
/merge |
/run-all-tests |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-e2e-tests |
@sre-bot merge failed. |
/run-e2e-tests |
/run-all-tests |
@sre-bot merge failed. |
/run-e2e-tests |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@sre-bot merge failed. |
/merge |
/run-all-tests |
@sre-bot merge failed. |
/merge |
/run-all-tests |
@sre-bot merge failed. |
/merge |
/run-all-tests |
@sre-bot merge failed. |
/merge |
/run-all-tests |
@sre-bot merge failed. |
/merge |
/run-all-tests |
cherry-pick #2249 to release-1.1
What problem does this PR solve?
Support failover for TiFlash
What is changed and how does it work?
Support failover for TiFlash
Check List
Tests
max-store-down-time
+tiflash-failover-period
),tc.status.tiflash.failureStores
will be updated and new TiFlash pod will be created.Code changes
Related changes
Does this PR introduce a user-facing change?: