Store got closed concurrently – How to solve this Elasticsearch error

Average Read Time

2 Mins

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 Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Store got closed concurrently”classname  is BlobStoreRepository.java 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 a demo of the Check-Up:

Analyze your cluster