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
Move cluster.routing.allocation.same_shard.host setting to new settings infrastructure #20046
Conversation
public static final String SAME_HOST_SETTING = "cluster.routing.allocation.same_shard.host"; | ||
public static final Setting<Boolean> CLUSTER_ROUTING_ALLOCATION_SAME_HOST_SETTING = | ||
Setting.boolSetting("cluster.routing.allocation.same_shard.host", false, | ||
Setting.Property.Dynamic, Setting.Property.NodeScope); |
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.
I'm unsure if this setting should be dynamic.
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.
As this setting should usually be only set once, it is probably simpler to leave it non-dynamic (as @jasontedor suggested and as it was before this PR). In case where this must absolutely be updated on a production cluster, rolling restart (of master nodes) with config update is always possible.
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.
Right. I wondered if it should be dynamic or not.
The reason I made it dynamic is document says it's dynamic.
(and thought making it dynamic maybe useful)
I'll make it non-dynamic.
67a2bd2
to
1e3678c
Compare
…gs infrastructure Fixes elastic#20045
1e3678c
to
c7e3653
Compare
@jasontedor @ywelsch Made it static (and rebased). Can you review it again? |
LGTM |
Thanks @s1monw. |
Fixes #20045