GetJobId Failed to close point in time reader – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.3-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 fails to close a point-in-time (PIT) reader, which is used for long-running searches. This could be due to a network issue, a bug, or a resource constraint. To resolve this, you can try restarting the Elasticsearch node, increasing system resources, or updating Elasticsearch to the latest version to fix potential bugs. Also, ensure that your application properly closes PIT readers after use to prevent resource leaks.

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 ” [” + getJobId() + “] Failed to close point in time reader ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[” + getJobId() + “] Failed to close point in time reader” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            ActionListener.wrap(response -> {
                logger.trace("[{}] closed pit search context [{}]"; getJobId(); oldPit);
            }; e -> {
                // note: closing the pit should never throw; even if the pit is invalid
                logger.error(() -> "[" + getJobId() + "] Failed to close point in time reader"; e);

    private void injectPointInTimeIfNeeded(


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?