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

Opster Team

Aug-23, Version: 7.15-8.2

Briefly, this error occurs when Elasticsearch is unable to close a point-in-time (PIT) reader, which is used for consistent search results during 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, checking for any network issues, or increasing the system resources. If the problem persists, consider upgrading Elasticsearch to the latest version as it might be a bug that has been fixed in a newer version.

This guide will help you check for common problems that cause the log ” [{}] 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 “[{}] 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(new ParameterizedMessage("[{}] Failed to close point in time reader"; getJobId()); 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?