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
Expose minimum_master_nodes in cluster state #37811
Expose minimum_master_nodes in cluster state #37811
Conversation
To safely support rolling upgrades from 6.x to 7.x we need the 7.x nodes to have access to the `minimum_master_nodes` setting, but this setting is otherwise unnecessary in 7.x and we would like to remove it. Since a rolling upgrade from 6.x to 7.x involves the 7.x nodes joining a 6.x master, we can avoid the need for setting `minimum_master_nodes` on the 7.x nodes by copying the value set on the 6.x master. This change exposes the master's node-level value for `minimum_master_nodes` via a field in the cluster state.
Pinging @elastic/es-distributed |
The parallel changes to |
This completes the BWC serialisation changes required for a 6.7 master to inform other nodes of the node-level value of the `minimum_master_nodes` setting. Relates elastic#37701, elastic#37811
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
@elasticmachine please run elasticsearch-ci/2 |
1 similar comment
@elasticmachine please run elasticsearch-ci/2 |
To safely support rolling upgrades from 6.x to 7.x we need the 7.x nodes to
have access to the
minimum_master_nodes
setting, but this setting isotherwise unnecessary in 7.x and we would like to remove it. Since a rolling
upgrade from 6.x to 7.x involves the 7.x nodes joining a 6.x master, we can
avoid the need for setting
minimum_master_nodes
on the 7.x nodes by copyingthe value set on the 6.x master.
This change exposes the master's node-level value for
minimum_master_nodes
via a field in the cluster state.
Relates #37701