Snapshot ” + snapName + ” not found in repository ” + repoName + ” – 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 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 ” snapshot ” + snapName + ” not found in repository ” + repoName + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repository, snapshot, plugin.

Log Context

Log “snapshot [” + snapName + “] not found in repository [” + repoName + “]”classname  is TransportMountSearchableSnapshotAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final Optional matchingSnapshotId = repoData.getSnapshotIds()
 .stream()
 .filter(s -> snapName.equals(s.getName()))
 .findFirst();
 if (matchingSnapshotId.isEmpty()) {
 throw new ElasticsearchException("snapshot [" + snapName + "] not found in repository [" + repoName + "]");
 }
 final SnapshotId snapshotId = matchingSnapshotId.get(); 
 final IndexMetadata indexMetadata = repository.getSnapshotIndexMetaData(repoData; snapshotId; indexId);
 if (indexMetadata.isSearchableSnapshot()) {

 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content