-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Clarify rolling-upgrade docs #47279
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
Clarify rolling-upgrade docs #47279
Conversation
Note to upgrade the master-eligible nodes last, and note that `cluster.initial_master_nodes` should not be set.
|
Pinging @elastic/es-distributed |
|
Pinging @elastic/es-docs |
jrodewig
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.
|
Relates #47028 |
jasontedor
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. Thanks for picking this up, we had discussed this quite a lot at an internal team meeting a couple of weeks ago.
Co-Authored-By: James Rodewig <[email protected]>
Note to upgrade the master-eligible nodes last, and note that `cluster.initial_master_nodes` should not be set.
Note to upgrade the master-eligible nodes last, and note that `cluster.initial_master_nodes` should not be set.
Note to upgrade the master-eligible nodes last, and note that `cluster.initial_master_nodes` should not be set.
Note to upgrade the master-eligible nodes last, and note that `cluster.initial_master_nodes` should not be set.
Note to upgrade the master-eligible nodes last, and note that `cluster.initial_master_nodes` should not be set.
Note to upgrade the master-eligible nodes last, and note that `cluster.initial_master_nodes` should not be set.
Note to upgrade the master-eligible nodes last, and note that
cluster.initial_master_nodesshould not be set.