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.
Overview
An Elasticsearch snapshot provides a backup mechanism that takes the current state and data in the cluster and saves it to a repository (read snapshot for more information). The backup process requires a repository to be created first. The repository needs to be registered using the _snapshot endpoint, and multiple repositories can be created per cluster. The following repository types are supported:
Repository types
| Repository type | Configuration type |
|---|---|
| Shared file system | Type: “fs” |
| S3 | Type : “s3” |
| HDFS | Type :“hdfs” |
| Azure | Type: “azure” |
| Google Cloud Storage | Type : “gcs” |
Examples
To register an “fs” repository:
PUT _snapshot/my_repo_01
{
"type": "fs",
"settings": {
"location": "/mnt/my_repo_dir"
}
}Notes and good things to know
- S3, HDFS, Azure and Google Cloud require a relevant plugin to be installed before it can be used for a snapshot.
- The setting, path.repo: /mnt/my_repo_dir needs to be added to elasticsearch.yml on all the nodes if you are planning to use the repo type of file system. Otherwise, it will fail.
- When using remote repositories, the network bandwidth and repository storage throughput should be high enough to complete the snapshot operations normally, otherwise you will end up with partial snapshots.
Log Context
Log “Store got closed concurrently” class name is SnapshotShardContext.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (commitRef.tryIncRef()) {
return Releasables.releaseOnce(commitRef::decRef);
} else {
snapshotStatus.ensureNotAborted();
assert false : "commit ref closed early in state " + snapshotStatus;
throw new IndexShardSnapshotFailedException(store.shardId(); "Store got closed concurrently");
}
}
}
