You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Dhritiman Das (JIRA)" <ji...@apache.org> on 2016/02/09 09:26:18 UTC

[jira] [Created] (SOLR-8663) Multiple searchers open for a single core causing memory issues

Dhritiman Das created SOLR-8663:
-----------------------------------

             Summary: Multiple searchers open for a single core causing memory issues
                 Key: SOLR-8663
                 URL: https://issues.apache.org/jira/browse/SOLR-8663
             Project: Solr
          Issue Type: Bug
    Affects Versions: 4.6
            Reporter: Dhritiman Das


For a single core, we are having multiple searchers open. Although the current searcher points to the latest searcher opened, some old searchers are not getting cleaned up , they are holding their cache and ultimately causing memory issues. 

Possibly for cores which are taking a lot of time to warmup their cache the replication interval is overlapping with warmup time taken for the last searcher open during last replication.

However any idea why sometimes old searchers are not getting freed ?
Ex. Searchers from couple of days back are still seen in Solr console.
ip:port/solr/admin.html#/<core-name>/plugins/core
Is there any known bug around this for Solr 4.6 ?

p.s.: we have custom code extending some Solr components at many places. What I am trying to understand also is what is the best place to start debugging this ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org