AUTO CREATE INDEX SETTING getKey is false – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-8.9

Briefly, this error occurs when the Elasticsearch setting “action.auto_create_index” is set to false. This setting controls whether Elasticsearch should automatically create an index when a write operation is attempted on a non-existing index. If it’s set to false, Elasticsearch will not create the index and will throw this error instead. To resolve this issue, you can either manually create the index before attempting the write operation, or you can change the “action.auto_create_index” setting to true, allowing Elasticsearch to automatically create the index when needed.

This guide will help you check for common problems that cause the log ” [” + AUTO_CREATE_INDEX_SETTING.getKey() + “] is [false] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “[” + AUTO_CREATE_INDEX_SETTING.getKey() + “] is [false]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  // One volatile read; so that all checks are done against the same instance:
 final AutoCreate autoCreate = this.autoCreate;
 if (autoCreate.autoCreateIndex == false) {
 throw new IndexNotFoundException("[" + AUTO_CREATE_INDEX_SETTING.getKey() + "] is [false]"; index);
 }  // matches not set; default value of "true"
 if (autoCreate.expressions.isEmpty()) {
 return true;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?