-
Notifications
You must be signed in to change notification settings - Fork 24.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
Rename no-master-block setting #38350
Rename no-master-block setting #38350
Conversation
Replaces `discovery.zen.no_master_block` with `cluster.no_master_block`. Any value set for the old setting is now ignored.
Pinging @elastic/es-distributed |
FAO @gwbrown as this is a breaking change. We explored a number of options for renaming this dynamic setting so as to fall back to the legacy setting name but all had drawbacks. Since this setting is very rarely adjusted, and only takes effect when the cluster is broken, we opted simply to start ignoring it in favour of the new name. |
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
@@ -103,7 +102,7 @@ | |||
private final JoinHelper joinHelper; | |||
private final NodeRemovalClusterStateTaskExecutor nodeRemovalExecutor; | |||
private final Supplier<CoordinationState.PersistedState> persistedStateSupplier; | |||
private final DiscoverySettings discoverySettings; |
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.
🕺
Thanks for the ping @DaveCTurner, I've added this to the list at #36024. This looks like a setting that would typically be set via the cluster settings API (rather than elasticsearch.yml), correct? |
TBH the overwhelmingly typical case is that this setting isn't set at all. I don't think we can say whether it's more or less likely to be set as a cluster setting vs a node setting. |
* master: Mute failing API key integration test (elastic#38409) Change the milliseconds precision to 3 digits for intervals. (elastic#38297) SecuritySettingsSource license.self_generated: trial (elastic#38233) Rename no-master-block setting (elastic#38350) Rename static Zen1 settings (elastic#38333) Migration doc for audit json log file (elastic#38165) Add apm_user reserved role (elastic#38206)
In elastic#38333 and elastic#38350 we moved away from the `discovery.zen` settings namespace since these settings have an effect even though Zen Discovery itself is being phased out. This change aligns the documentation and the names of related classes and methods with the newly-introduced naming conventions.
Zen discovery and its associated settings were deprecated in 7.0. This commit adds an entry to the release notes calling this out. Relates elastic#38289 elastic#38333 elastic#38350 elastic#37868
Replaces
discovery.zen.no_master_block
withcluster.no_master_block
. Anyvalue set for the old setting is now ignored.