Attempting to remove non-existent snapshots from repository data – 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 analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

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


Log Context

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

Map newSnapshotIds = snapshotIds.values().stream().filter(Predicate.not(snapshots::contains))
 .collect(Collectors.toMap(SnapshotId::getUUID; Function.identity()));
 if (newSnapshotIds.size() != snapshotIds.size() - snapshots.size()) {
 final Collection notFound = new HashSet<>(snapshots);
 throw new ResourceNotFoundException("Attempting to remove non-existent snapshots {} from repository data"; notFound);
 Map newSnapshotStates = new HashMap<>(snapshotStates);
 final Map newSnapshotVersions = new HashMap<>(snapshotVersions);
 for (SnapshotId snapshotId : snapshots) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content