Skip to content

Only use InitialMasterNodes during bootstrap #85929

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.

Sign up for GitHub

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

Closed
Parent: fix stale data in synthetic source for string stored field
wants to merge 1 commit into from
Closed

Only use InitialMasterNodes during bootstrap #85929

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/reference/modules/discovery/bootstrapping.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ node:

When you start a master-eligible node, you can provide this setting on the
command line or in the `elasticsearch.yml` file. After the cluster has formed,
this setting is no longer required. It should not be set for master-ineligible
this setting should no longer be used. It should not be set for master-ineligible
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's still weaker than it could be. How about making it a command to the user, like this?

Suggested change
this setting should no longer be used. It should not be set for master-ineligible
remove this setting from the configuration. It should not be set for master-ineligible

nodes, master-eligible nodes joining an existing cluster, or cluster restarts.

It is technically sufficient to set `cluster.initial_master_nodes` on a single
Expand Down