-
Notifications
You must be signed in to change notification settings - Fork 732
Correct distconf quorum for scenario when user adds new nodes to cluster #28455
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
Correct distconf quorum for scenario when user adds new nodes to cluster #28455
Conversation
|
⚪ |
|
⚪ |
|
🟢 |
5c2d6d6 to
819e588
Compare
|
⚪ |
|
⚪ |
819e588 to
aeb93dd
Compare
|
⚪ |
|
⚪ |
aeb93dd to
6115328
Compare
|
⚪ |
|
⚪ |
6115328 to
de24241
Compare
de24241 to
4284068
Compare
|
⚪ |
|
⚪ |
4284068 to
325974d
Compare
|
⚪ |
|
⚪
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
325974d to
f5d3e12
Compare
f5d3e12 to
5a4e086
Compare
|
⚪ ⚪ Ya make output | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
|
⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
mregrock
left a comment
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
Changelog entry
Correct distconf quorum for scenario when user adds new nodes to cluster
Changelog category
Description for reviewers
This patch corrects adding new nodes scenario. Now distconf connects to these nodes and writes config to them before making quorum decision.