Attempting to remove non-existent snapshot from repository data – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.7

Briefly, this error occurs when Elasticsearch tries to delete a snapshot that doesn’t exist in the specified repository. This could be due to a typo in the snapshot name or the snapshot was already deleted. To resolve this, ensure the snapshot name is correct and exists in the repository. If the snapshot was already deleted, no action is needed. If the error persists, check the repository’s health and configuration.

This guide will help you check for common problems that cause the log ” Attempting to remove non-existent snapshot [{}] from repository data ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: snapshot, repositories, repository.

Log Context

Log “Attempting to remove non-existent snapshot [{}] from repository data” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public RepositoryData removeSnapshot(final SnapshotId snapshotId; final ShardGenerations updatedShardGenerations) {
 Map newSnapshotIds = snapshotIds.values().stream()
 .filter(id -> !snapshotId.equals(id))
 .collect(Collectors.toMap(SnapshotId::getUUID; Function.identity()));
 if (newSnapshotIds.size() == snapshotIds.size()) {
 throw new ResourceNotFoundException("Attempting to remove non-existent snapshot [{}] from repository data"; snapshotId);
 Map newSnapshotStates = new HashMap<>(snapshotStates);
 final Map newSnapshotVersions = new HashMap<>(snapshotVersions);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?