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

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 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. 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: 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 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”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);

 

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

Analyze your cluster