Store got closed concurrently – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.9-8.9

Briefly, this error occurs when an Elasticsearch index store is closed while it’s still being accessed by another process. This could be due to a race condition or an abrupt shutdown of the Elasticsearch node. To resolve this issue, you can try restarting the Elasticsearch node, ensuring that no other processes are accessing the index store during shutdown. If the error persists, consider checking your cluster health and rebalancing your indices. You may also need to check your application code to ensure it’s properly handling connections to Elasticsearch.

This guide will help you check for common problems that cause the log ” Store got closed concurrently ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories.

Log Context

Log “Store got closed concurrently” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (commitRef.tryIncRef()) {
 return Releasables.releaseOnce(commitRef::decRef);
 } else {
 assert false : "commit ref closed early in state " + snapshotStatus;
 throw new IndexShardSnapshotFailedException(store.shardId(); "Store got closed concurrently");