Auto-creating indices even though configured not to

[simonauner-bookbeat (Simon Aunér)]

I want to have full control over what indices are created in my cluster, so I have configured

PUT _cluster/settings
{
    "persistent": {
        "action.auto_create_index": "false" 
    }
}

Still, when using NEST to send a BulkUpdateOperation, indices are auto-created, but I expect them to return 404.

new BulkUpdateOperation<RankedDto, Dto>(
          new RankedDto { Id = dto.Id }, dto, true) 
         {Index = "something_something"}

This operation gives me a 201 with index "something_something" created, even though I would expect it to give me a 404.

Do I need to configure something else as well?

I'm using Elastic Cloud 7.6.1

[spinscale (Alexander Reelsen)]

Hey,

you can change that setting under your deployment in the "Edit" part and then search for Elasticsearch plugins and settings - there is a checkbox to select this.

--Alex

[simonauner-bookbeat (Simon Aunér)]

@spinscale Ok, thanks! That seems to affect both

"persistent": {
        "action.auto_create_index": "false" 
    }

and

"transient": {
        "action.auto_create_index": "false" 
    }

so perhaps that was the answer I was looking for.

In other words: this is not enough:

PUT _cluster/settings
{
    "persistent": {
        "action.auto_create_index": "false" 
    }
}

This should be correct:

PUT _cluster/settings
{
    "persistent": {
        "action.auto_create_index": "false" 
    },
  "transient": {
        "action.auto_create_index": "false" 
    }
}

thanks!