Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.
Briefly, this error occurs when the auto_create_index setting in OpenSearch is set to false. This setting controls whether new indices should be automatically created when a document is indexed into a non-existing index. If set to false, indexing a document into a non-existing index will fail. To resolve this issue, you can either manually create the index before indexing documents into it, or you can change the auto_create_index setting to true or to a pattern that matches the index you want to auto-create.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
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 OpenSearch concepts: .
Log Context
Log “[” + AUTO_CREATE_INDEX_SETTING.getKey() + “] is [false]” class name is AutoCreateIndex.java. We extracted the following from OpenSearch 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);
}
if (dynamicMappingDisabled) {
throw new IndexNotFoundException("[" + MapperService.INDEX_MAPPER_DYNAMIC_SETTING.getKey() + "] is [false]"; index);
}
// matches not set; default value of "true"
