Snapshot does not exist – How to solve this Elasticsearch error

Average Read Time

2 Mins

Snapshot does not exist – How to solve this Elasticsearch error

Opster Team

March-22, 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 does not exist ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: snapshot.

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 does not exist”classname  is RestoreService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final Optional matchingSnapshotId = repositoryData.getSnapshotIds()
 .stream()
 .filter(s -> snapshotName.equals(s.getName()))
 .findFirst();
 if (matchingSnapshotId.isPresent() == false) {
 throw new SnapshotRestoreException(repositoryName; snapshotName; "snapshot does not exist");
 } 
 final SnapshotId snapshotId = matchingSnapshotId.get();
 if (request.snapshotUuid() != null && request.snapshotUuid().equals(snapshotId.getUUID()) == false) {
 throw new SnapshotRestoreException(

 

Watch a demo of the Check-Up:

Analyze your cluster