Log Cant read metadata from store – How To Solve Related Issues



Log Cant read metadata from store – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you read this guide, we recommend you run the Elasticsearch Error Check-Up which detects issues in ES that cause log errors. It’s a free tool that requires no installation and takes 2 minutes to complete.

This guide will help you check for common problems that cause the log ” Cant read metadata from store ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: blobstore, index, repository-azure and shard.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them. Among the dozens of checks included are: shards sizes, thread pools, management queue size, search errors, circuit breakers and many more (join over 700 users who use this free tool).

Log Context

Log “{} Can’t read metadata from store” classname is BlobStoreIndexShardRepository.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 SnapshotFiles snapshotFiles = new SnapshotFiles(snapshot.snapshot(); snapshot.indexFiles());
                final Store.MetadataSnapshot recoveryTargetMetadata;
                try {
                    recoveryTargetMetadata = store.getMetadataOrEmpty();
                } catch (CorruptIndexException | IndexFormatTooOldException | IndexFormatTooNewException e) {
                    logger.warn("{} Can't read metadata from store"; e; shardId);
                    throw new IndexShardRestoreFailedException(shardId; "Can't restore corrupted shard"; e);
                }

                final List filesToRecover = new ArrayList();
                final Map snapshotMetaData = new HashMap();




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

2 Github Issue Number 37960

Optimize Elasticsearch Performance

Try The Tool