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 Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content