lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3392) searcher leak
Date Sat, 21 Apr 2012 19:10:34 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258929#comment-13258929
] 

Yonik Seeley commented on SOLR-3392:
------------------------------------

bq. But they do? There were a number of failures when the number of closes/opens mismatched
and failed the build.

Those normally don't fail on my box - just our Jenkins box which is really slow + has weird
stuff like blackhole configured.  Talking to Mark, it sounds like the cause of those open/close
searcher mismatches are because another thread is still running (like a recovery/replication
thread) and still has a searcher open (hence it doesn't look like a searcher management bug).

The type of bug I'm looking at would be a searcher management bug not related to thread safety
and should be 100% reproducible.
                
> searcher leak
> -------------
>
>                 Key: SOLR-3392
>                 URL: https://issues.apache.org/jira/browse/SOLR-3392
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Yonik Seeley
>
> It appears we have a searcher leak where SolrIndexSearcher instances are sometimes not
being closed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message