-
Notifications
You must be signed in to change notification settings - Fork 314
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
scale-in pd leader after evict the leader #2005
scale-in pd leader after evict the leader #2005
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Codecov Report
@@ Coverage Diff @@
## master #2005 +/- ##
===========================================
- Coverage 52.61% 40.91% -11.70%
===========================================
Files 308 288 -20
Lines 35878 33507 -2371
===========================================
- Hits 18874 13707 -5167
- Misses 14785 17988 +3203
+ Partials 2219 1812 -407
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: c061391
|
What problem does this PR solve?
close #2015
This can help TiCDC be more robust to PD leader change, replication latency does not goes up, since there is always a pd leader to contact for make progress.
What is changed and how it works?
transfer the pd leadership, before scale-in pd leader node.
Check List
Tests
Code changes
Side effects
Related changes
Release notes: