Searcher was released twice – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when an Elasticsearch searcher instance is closed or released more than once. This can happen due to a programming error where the release method is called multiple times on the same searcher instance. To resolve this issue, you should review your code to ensure that each searcher instance is only released once. Also, consider using a try-with-resources block or similar construct to manage the lifecycle of your searcher instances. This will help prevent them from being released multiple times.

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

Log Context

Log “Searcher was released twice” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                } else {
                    /* In general; searchers should never be released twice or this would break reference counting. There is one rare case
                     * when it might happen though: when the request and the Reaper thread would both try to release it in a very short
                     * amount of time; this is why we only log a warning instead of throwing an exception. */
                    logger.warn("Searcher was released twice"; new IllegalStateException("Double release"));
            releasable = null; // success - hand over the reference to the engine searcher
            return engineSearcher;
        } catch (AlreadyClosedException ex) {


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?