-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Bootstrapping docs clarifications #94977
Bootstrapping docs clarifications #94977
Conversation
Explains why you should remove `cluster.initial_master_nodes`, and rewords some of the other sections a little for (subjectively) improved readability.
Documentation preview: |
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-distributed (Team:Distributed) |
Like all node settings, it is also possible to specify the initial set of master | ||
nodes on the command-line that is used to start Elasticsearch: |
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.
We've removed most mention of this from elsewhere in the docs, I suspect because it only works for certain installation methods. No need to say it here either.
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 fixing these up!
Explains why you should remove `cluster.initial_master_nodes`, and rewords some of the other sections a little for (subjectively) improved readability.
💚 Backport successful
|
In elastic#94977 we tried to introduce a multi-paragraph admonition using a list continuation (`+`) but this doesn't work. This commit fixes the mistake using an admonition block instead.
Explains why you should remove
cluster.initial_master_nodes
, and rewords some of the other sections a little for (subjectively) improved readability.