Snapshot does not exist – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when you try to restore or delete a snapshot in Elasticsearch that does not exist. This could be due to a typo in the snapshot name or the snapshot was already deleted. To resolve this issue, you can verify the snapshot name and ensure it exists by using the “GET _snapshot/repository_name/snapshot_name” API. If the snapshot was deleted, you may need to create a new one. Always ensure to keep track of your snapshots to avoid such 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.

Log Context

Log “snapshot does not exist” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 final Optional matchingSnapshotId = repositoryData.getSnapshotIds()
 .filter(s -> snapshotName.equals(s.getName()))
 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(