Snapshot could not be read – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

Briefly, this error occurs when Elasticsearch is unable to read a snapshot, which is a backup of the index data. This can be due to a variety of reasons, including corruption of the snapshot file, incorrect permissions, or network issues. To resolve this issue, you can try restoring the snapshot from a different source, checking the permissions on the snapshot files, or looking into any network issues.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Snapshot could not be read ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, snapshot and cluster.

Log Context

Log “Snapshot could not be read”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

logger.warn(() -> new ParameterizedMessage("failed to get snapshot [{}]"; snapshotId); ex);
 } else {
 if (ex instanceof SnapshotException) {
 throw ex;
 throw new SnapshotException(repositoryName; snapshotId; "Snapshot could not be read"; ex);
 final ArrayList snapshotList = new ArrayList<>(snapshotSet);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content