Elasticsearch: action.auto_create_index isn't a dynamic setting

[nik9000]

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?

[clintongormley]

Hmm - not sure this should be a dynamic setting...

[clintongormley]

@javanna any thoughts on this?

[javanna]

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 :)

[clintongormley]

@javanna my thinking exactly :)

Anybody else disagree? otherwise i think we should close this

[nik9000]

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 false to a whitelist pattern but if I can't change the pattern on the fly I have to schedule the change to go with the next rolling restart.

[clintongormley]

I wasn't aware that you _could_ specify a pattern! This makes me lean more towards making it dynamic.

[bleskes]

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]
wrote:

I wasn't aware that you _could_ specify a pattern! This makes me lean more towards making it dynamic.

Reply to this email directly or view it on GitHub:
https://github.com/elasticsearch/elasticsearch/issues/7513#issuecomment-54976283

[synhershko]

+1 for making this dynamic, at least if its on the pattern mode (and not just false)

[pmusa]

+1 for that as a dynamic setting. I am trying to set it in found and it is not possible currently.

[djschny]

+1 for this, it also helps avoid node level configuration inconsistency.

[frivoire]

(I'm fairly new to the ES world but) this setting seems more like a cluster-wide dynamic setting to me.

[itplayer]

I hope this setting can be a cluster-wide setting.
The reason is, if a node client setting is true(or lack of setting), but other nodes in cluster is false, then unexpected result happen.