Index ” + ((IndexNotFoundException) e).getIndex() + ” was not found; – 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.

Briefly, this error message indicates that Elasticsearch is unable to find the specified index. This can occur if the index does not exist, or if the user does not have sufficient permissions to access the index. To resolve this error, ensure that the index exists and that the user has the necessary permissions to access it.

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.

This guide will help you check for common problems that cause the log ” Index ” + ((IndexNotFoundException) e).getIndex() + ” was not found; ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index and plugin.

Log Context

Log “Index [” + ((IndexNotFoundException) e).getIndex() + “] was not found;”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (item.isFailure()) {
 Exception e = item.getFailure(); 
 // If an index was deleted after execution; give a hint to the user that this is a transient error
 if (e instanceof IndexNotFoundException) {
 throw new ResourceNotFoundException("Index [" + ((IndexNotFoundException) e).getIndex() + "] was not found; " +
 "likely because it was deleted while the request was in-flight. Rollup does not support partial search results; " +
 "please try the request again."; e);
 // Otherwise just throw


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content