Failed to read metadata for index – 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 for a specific index. This could be due to corruption in the index, insufficient permissions, or a disk I/O error. To resolve this issue, you can try the following: 1) Check and repair the index if it’s corrupted. 2) Verify and adjust the permissions if necessary. 3) Check the disk for errors and fix them. 4) If the index is not needed, consider deleting it. Always ensure to have a backup before performing these operations.

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

Log Context

Log “[{}] [{}] failed to read metadata for index” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             BlobContainer indexMetaDataBlobContainer = blobStore().blobContainer(indexPath);
            try {
                metaDataBuilder.put(indexMetaDataFormat(snapshotVersion).read(indexMetaDataBlobContainer; snapshotId.getSnapshot()); false);
            } catch (ElasticsearchParseException | IOException ex) {
                if (ignoreIndexErrors) {
                    logger.warn("[{}] [{}] failed to read metadata for index"; ex; snapshotId; index);
                } else {
                    throw ex;


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?