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

Average Read Time

2 Mins

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 Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Snapshot could not be read”classname  is TransportGetSnapshotsAction.java 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);
 CollectionUtil.timSort(snapshotList);

 

Watch a demo of the Check-Up:

Analyze your cluster