Log Searcher was released twice – How To Solve Related Issues


Log Searcher was released twice – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Searcher was released twice ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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) {




 

Optimize Elasticsearch Performance

Try The Tool