Log Searcher was released twice – How To Solve Related Issues

Log Searcher was released twice – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “Searcher was released twice” it’s important to understand a few problems related to Elasticsearch concepts index. See bellow important tips and explanations on these concepts

Log Context

Log”Searcher was released twice” classname is Engine.java
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) {




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 ElasticSearch .NET

0.86 K 1

To Sort Search Results On Multiple  

 

About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now