How To Solve Issues Related to Log – Cant read metadata from store; will not reuse local files during restore

Get an Elasticsearch Check-Up

Check if your ES issues are caused from misconfigured settings
(Free 2 min process)


Last update: Jan-20

Elasticsearch Error Guide In Page Navigation (click to jump) :

Troubleshooting Background – start here to get the full picture       
Related Issues – selected resources on related issues  
Log Context – usefull for experts
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check Your Elasticsearch Settings for Painfull Mistakes 

Troubleshooting background

To troubleshoot Elasticsearch log “Cant read metadata from store; will not reuse local files during restore” it’s important to know common problems related to Elasticsearch concepts: blobstore, discovery-file, repositories, restore. See below-detailed explanations complete with common problems, examples and useful tips.

Repositories/Repository in Elasticsearch

What it is

An Elasticsearch snapshot provides a backup mechanism that takes the current state and data in the cluster and saves it to a repository (read the Glossary term 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 per cluster can be created. The following repository types are supported. 

Repository Types:
Repository TypeConfiguration Type
Shared file systemType: “fs”
S3Type : “s3”
HDFSType :“hdfs”
AzureType: “azure”
Google Cloud StorageType : “gcs”

To register a repository of type fs:

PUT _snapshot/my_repo_01
"type": "fs",
"settings": {
"location": "/mnt/my_repo_dir"
Notes and common problems
  • S3, HDFS , Azure and Google Cloud requires 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 in case you are planning to use repo type of file system otherwise it will fail
  • In case of 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 in partial snapshots.

To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

At Does Stale File Handle In Linux


Github Issue Number 37960


Log Context

Log ”Cant read metadata from store; will not reuse local files during restore” classname is
We have extracted the following from Elasticsearch source code to get an in-depth context :

<pre class="wp-block-syntaxhighlighter-code">             } catch (org.apache.lucene.index.IndexNotFoundException e) {
                // happens when restore to an empty shard; not a big deal
                logger.trace("[{}] [{}] restoring from to an empty shard"; shardId; snapshotId);
                recoveryTargetMetadata = Store.MetadataSnapshot.EMPTY;
            } catch (IOException e) {
                logger.warn(new ParameterizedMessage("[{}] [{}] Can't read metadata from store; will not reuse local files during restore";
                    shardId; snapshotId); e);
                recoveryTargetMetadata = Store.MetadataSnapshot.EMPTY;

            final List<BlobStoreIndexShardSnapshot.FileInfo> filesToRecover = new ArrayList<>();


About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues

We are constantly updating our analysis of Elasticsearch logs, errors, and exceptions. Sharing best practices and providing troubleshooting guides.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?