Cannot read metadata for snapshot – How to solve related issues

Cannot read metadata for snapshot – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Cannot read metadata for snapshot ” 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, metadata, repositories, repository-azure and snapshot.

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 (free tool that requires no installation).

Log Context

Log “cannot read metadata for snapshot [{}]” classname is BlobStoreRepository.java.
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());




 

Run the Check-Up to get a customized report like this:

Analyze your cluster