No index state found – ignoring – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 5-5

Briefly, this error occurs when Elasticsearch cannot find the state of a specific index. This could be due to the index being deleted or not yet created. To resolve this issue, you can check if the index exists before performing operations. If it doesn’t, create the index first. Alternatively, you can handle this error in your application code by catching the exception and taking appropriate action, such as retrying the operation or logging the error for further investigation.

This guide will help you check for common problems that cause the log ” [{}] no index state found – ignoring ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “[{}] no index state found – ignoring” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     upgrade(index; indexFolderPath; indexFolderPath.resolveSibling(index.getUUID()));
                } else {
                    logger.debug("[{}] no upgrade needed - already upgraded"; indexFolderPath);
            } else {
                logger.warn("[{}] no index state found - ignoring"; indexFolderPath);



How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?