Store got closed concurrently – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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, blobstore.

Log Context

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

if (store.tryIncRef() == false) {
 if (snapshotStatus.isAborted()) {
 throw new AbortedSnapshotException();
 } else {
 assert false : "Store should not be closed concurrently unless snapshot is aborted";
 throw new IndexShardSnapshotFailedException(shardId; "Store got closed concurrently");
 return store::decRef;


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content