Index indexName not found in repository repoName – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.8-8.9

Briefly, this error occurs when Elasticsearch is unable to locate the specified index in the given repository. This could be due to the index being deleted, renamed, or not existing in the first place. To resolve this issue, you can verify the index name and repository name for any typos or case sensitivity issues. If the index was deleted, you may need to restore it from a backup. If the index never existed, you should create it before proceeding.

This guide will help you check for common problems that cause the log ” index [” + indexName + “] 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, plugin, index.

Log Context

Log “index [” + indexName + “] not found in repository [” + repoName + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 final ListenableFuture repositoryDataListener = new ListenableFuture<>();
 repositoryDataListener.addListener(ActionListener.wrap(repoData -> {
 final Map indexIds = repoData.getIndices();
 if (indexIds.containsKey(indexName) == false) {
 throw new IndexNotFoundException("index [" + indexName + "] not found in repository [" + repoName + "]");
 final IndexId indexId = indexIds.get(indexName);  final Optional matchingSnapshotId = repoData.getSnapshotIds()