How To Solve Issues Related to Log – Failed to read metadata for index

How To Solve Issues Related to Log – Failed to read metadata for index

Updated: Feb-20

Elasticsearch Version: 1.7-8.0


Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.

To troubleshoot log “Failed to read metadata for index” it’s important to understand a few problems related to Elasticsearch concepts blobstore, index, metadata, repositories, repository-azure. See bellow important tips and explanations on these concepts

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;

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 :


Elasticsearch crashes after showing t: failed to read local state , exiting

  2.27 K 2

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now