-
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
action.auto_create_index isn't a dynamic setting #7513
Comments
Hmm - not sure this should be a dynamic setting... |
@javanna any thoughts on this? |
not sure either, it currently is a node level static setting, we could make it a cluster dynamic setting, but I think the rationale behind this choice was that one should not be able to change it dynamically. I'm conflicted here :) |
@javanna my thinking exactly :) Anybody else disagree? otherwise i think we should close this |
My reasoning for wanting it is that I tend to use it to prevent accidental index creation. My requirements changed slightly in that I have change it from a |
I wasn't aware that you could specify a pattern! This makes me lean more towards making it dynamic. |
IMHO this should be dynamic. In my opinion this more of an error prevention feature than a security measure. We should opt for conveniance here for the operator. If you can call this end point you can create havoc anyway so i don't think we this plays as an argument here. On Tue, Sep 9, 2014 at 4:23 PM, Clinton Gormley [email protected]
|
+1 for making this dynamic, at least if its on the pattern mode (and not just |
+1 for that as a dynamic setting. I am trying to set it in found and it is not possible currently. |
+1 for this, it also helps avoid node level configuration inconsistency. |
(I'm fairly new to the ES world but) this setting seems more like a cluster-wide dynamic setting to me. |
I hope this setting can be a cluster-wide setting. |
We changed the `action.auto_create_index` setting to be a dynamic cluster-level setting in elastic#20274 but today the reference manual indicates that it is still a static node-level setting. This commit addresses this, and clarifies the semantics of patterns that may both permit and forbid the creation of certain indices. Relates elastic#7513
We changed the `action.auto_create_index` setting to be a dynamic cluster-level setting in #20274 but today the reference manual indicates that it is still a static node-level setting. This commit addresses this, and clarifies the semantics of patterns that may both permit and forbid the creation of certain indices. Relates #7513
We changed the `action.auto_create_index` setting to be a dynamic cluster-level setting in #20274 but today the reference manual indicates that it is still a static node-level setting. This commit addresses this, and clarifies the semantics of patterns that may both permit and forbid the creation of certain indices. Relates #7513, #27026
We changed the `action.auto_create_index` setting to be a dynamic cluster-level setting in #20274 but today the reference manual indicates that it is still a static node-level setting. This commit addresses this, and clarifies the semantics of patterns that may both permit and forbid the creation of certain indices. Relates #7513, #27026
We changed the `action.auto_create_index` setting to be a dynamic cluster-level setting in #20274 but today the reference manual indicates that it is still a static node-level setting. This commit addresses this, and clarifies the semantics of patterns that may both permit and forbid the creation of certain indices. Relates #7513, #27026
We changed the `action.auto_create_index` setting to be a dynamic cluster-level setting in #20274 but today the reference manual indicates that it is still a static node-level setting. This commit addresses this, and clarifies the semantics of patterns that may both permit and forbid the creation of certain indices. Relates #7513, #27026
We changed the `action.auto_create_index` setting to be a dynamic cluster-level setting in #20274 but today the reference manual indicates that it is still a static node-level setting. This commit addresses this, and clarifies the semantics of patterns that may both permit and forbid the creation of certain indices. Relates #7513, #27026
We changed the `action.auto_create_index` setting to be a dynamic cluster-level setting in #20274 but today the reference manual indicates that it is still a static node-level setting. This commit addresses this, and clarifies the semantics of patterns that may both permit and forbid the creation of certain indices. Relates #7513, #27026
We changed the `action.auto_create_index` setting to be a dynamic cluster-level setting in #20274 but today the reference manual indicates that it is still a static node-level setting. This commit addresses this, and clarifies the semantics of patterns that may both permit and forbid the creation of certain indices. Relates #7513, #27026
We changed the `action.auto_create_index` setting to be a dynamic cluster-level setting in #20274 but today the reference manual indicates that it is still a static node-level setting. This commit addresses this, and clarifies the semantics of patterns that may both permit and forbid the creation of certain indices. Relates #7513, #27026
Looks like
action.auto_create_index
can't be set dynamically as it isn't listed in ClusterDynamicSettingsModule.java. Any objection to me adding it?The text was updated successfully, but these errors were encountered: