Can t read metadata from store – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is unable to read the metadata from the data store. This could be due to corruption in the data store, insufficient permissions, or a network connectivity issue. To resolve this, you can try restoring from a backup, checking and adjusting the file permissions, or troubleshooting the network connection. If the data store is corrupted, you may need to delete and recreate it. Always ensure to have a backup strategy in place to prevent data loss.

This guide will help you check for common problems that cause the log ” {} Can’t read metadata from store ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, index, repository-azure and shard.

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();




 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?