-
Notifications
You must be signed in to change notification settings - Fork 720
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
*: Bug Fix/CLUSTER_INFO system table may not work after PD is scaled-in #2830
Conversation
Signed-off-by: jyz0309 <45495947@qq.com>
3792906
to
de33264
Compare
/rebuild |
Signed-off-by: jyz0309 <45495947@qq.com>
8e57a9b
to
c0c6590
Compare
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.
Rest LGTM
Signed-off-by: jyz0309 <45495947@qq.com>
…-fix/pd_scale_bug to update
/rebuild |
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
/merge |
/run-all-tests |
I think |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-4.0 in PR #2980 |
What problem does this PR solve?
Issue Number: close pingcap/tidb#18990
Problem Summary:
CLUSTER_INFO system table may not work after PD is scaled-in
What is changed and how it works?
What's Changed:
Add the GetMemberInfo function to client interface, use grpc GetMembers() to get the pd members info.
How it Works:
use grpc GetMembers() to get the pd members info.
Related changes
pingcap/pd/client/client.go
;Check List
Tests
steps:
select * from INFORMATION_SCHEMA.CLUSTER_INFO;
to test scale out and scale inSide effects
Release note