Failed to create new reader – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is unable to create a new reader due to issues like insufficient system resources, corrupted indices, or incorrect file permissions. To resolve this, you can try increasing system resources, repairing or deleting corrupted indices, or checking and correcting file permissions. Additionally, ensure that the Elasticsearch process has the necessary read/write permissions to the data directory.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” failed to create new reader ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “failed to create new reader” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     throw new IllegalStateException("failed to open a shadow engine after" +
                            nonexistentRetryTime + "ms; " +
                            "directory is not an index");
            } catch (Throwable e) {
                logger.warn("failed to create new reader"; e);
                throw e;
            } finally {
                if (success == false) {


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?