Failed to close reader – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.4-8.9

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 close an open index reader, possibly due to a network issue, a bug, or a resource constraint. To resolve this issue, you can try restarting the Elasticsearch node, checking for any network issues, or increasing the system resources. If the problem persists, consider checking the Elasticsearch logs for more detailed error information. It might also be helpful to upgrade Elasticsearch to the latest version, as this could be a bug that has been fixed in a newer release.

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 close 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 close reader” classname is ReadOnlyEngine.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    protected void closeNoLock(String reason; CountDownLatch closedLatch) {
        if (isClosed.compareAndSet(false; true)) {
            try {
                IOUtils.close(readerManager; indexWriterLock; store::decRef);
            } catch (Exception ex) {
                logger.warn("failed to close reader"; ex);
            } finally {
                closedLatch.countDown();
            }
        }
    }

 

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?