Failed to get store file metadata – How to solve this Elasticsearch error

Average Read Time

2 Mins

Failed to get store file metadata – 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 ” Failed to get store file metadata ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, metadata, 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 “Failed to get store file metadata”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

try {
 logger.trace("[{}] [{}] Loading store metadata using index commit [{}]"; shardId; snapshotId; snapshotIndexCommit);
 metadataFromStore = store.getMetadata(snapshotIndexCommit);
 fileNames = snapshotIndexCommit.getFileNames();
 } catch (IOException e) {
 throw new IndexShardSnapshotFailedException(shardId; "Failed to get store file metadata"; e);
 for (String fileName : fileNames) {
 if (snapshotStatus.isAborted()) {
 logger.debug("[{}] [{}] Aborted on the file [{}]; exiting"; shardId; snapshotId; fileName);


Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content