Index IndexNotFoundException e getIndex was not found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.2-7.15

Briefly, this error occurs when Elasticsearch tries to access an index that does not exist. This could be due to a typo in the index name, or the index may have been deleted. To resolve this issue, you can check the index name for typos, ensure the index exists before performing operations, or handle the IndexNotFoundException in your code to provide a more user-friendly error message. You could also consider using an alias for your indices to prevent direct references to specific index names.

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: plugin, index.

Log Context

Log “Index [” + ((IndexNotFoundException) e).getIndex() + “] was not found; ” class name 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