Temp index should not trigger store creation – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.8-8.9

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 Elasticsearch operation.

Briefly, this error occurs when Elasticsearch attempts to create a store for a temporary index, which is not a standard operation. Temporary indices are usually used for transient operations and do not require a store. This could be due to a misconfiguration or a bug in the software. To resolve this issue, you can try to identify and correct the misconfiguration causing this error, upgrade Elasticsearch to the latest version to fix potential bugs, or consult with the Elasticsearch community or support for further assistance.

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 ” temp index should not trigger store creation [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, indices.

Log Context

Log “temp index should not trigger store creation [{}]” class name is IndicesService.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  @Override
 public void onStoreCreated(ShardId shardId) {
 assert false : "temp index should not trigger store creation";
 throw new ElasticsearchException("temp index should not trigger store creation [{}]"; index);
 final IndexService indexService = createIndexService(


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?

Get expert answers on Elasticsearch/OpenSearch