Cannot read metadata for snapshot – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is unable to access or read the metadata associated with a specific snapshot. This could be due to issues with the snapshot repository, such as incorrect configuration, permission issues, or network connectivity problems. To resolve this, you can verify the repository configuration, ensure the Elasticsearch process has the necessary permissions to access the repository, and check network connectivity. Additionally, the snapshot metadata could be corrupted, in which case you may need to delete and recreate the snapshot.

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

Log Context

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

                 metaData = readSnapshotMetaData(snapshotId; snapshot.version(); indices; true);
            } else {
                metaData = readSnapshotMetaData(snapshotId; null; indices; true);
        } catch (IOException | SnapshotException ex) {
            logger.warn("cannot read metadata for snapshot [{}]"; ex; snapshotId);
        try {
            // Delete snapshot file first so we wouldn't end up with partially deleted snapshot that looks OK
            if (snapshot != null) {
                snapshotFormat(snapshot.version()).delete(snapshotsBlobContainer; snapshotId.getSnapshot());


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?