-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
[3.4] Allow new server to join higher cluster version if NextClusterVersionCompatible is true #17665
Conversation
…atible is true Signed-off-by: Siyuan Zhang <[email protected]>
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
Please at least manually verify: add a 3.4 member (with NextClusterVersionCompatible
enabled) into a 3.5 cluster for now.
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 - Thanks @siyuanfoundation
Note: We will need to update https://github.com/etcd-io/website/blob/main/content/en/docs/v3.4/op-guide/configuration.md also. We can make it a good first issue for a community member perhaps.
Sounds good. Created good first issue #17671 |
verified manually
|
Thanks for the verification. |
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.
Part of #15878 (comment).
#17330 allows existing server to be downgraded to 3.4, with
haveWAL=true
.This PR would allow a brand new 3.4 server to join an existing 3.5 cluster.
This would enable the downgrade method of stopping a 3.5 server and starting a new 3.4 server one by one.
Tested with
TestMixVersionsSnapshotByAddingMember
e2e test in #17531