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

Cyrille Roy edited comment on SOLR-2927 at 11/7/14 3:40 PM:
------------------------------------------------------------

the deadlock in our 4_2 branch occurs when doing infoRegistry.​clear(); after 
close​Searcher().
I'll integrate the patch taking this into account.
Thanks again [~shalinmangar] for the great work and feedback.


was (Author: croy):
the deadlock in our 4_2 branch occurs when doing infoRegistry.​clear(); after 
close​Searcher().
I'll integrate taking this into account.
Thanks again [~shalinmangar] for the great work and feedback.

> SolrIndexSearcher's register do not match close and SolrCore's closeSearcher
> ----------------------------------------------------------------------------
>
>                 Key: SOLR-2927
>                 URL: https://issues.apache.org/jira/browse/SOLR-2927
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 4.0-ALPHA
>         Environment: JDK1.6/CentOS
>            Reporter: tom liu
>            Assignee: Shalin Shekhar Mangar
>             Fix For: 5.0, Trunk
>
>         Attachments: SOLR-2927.patch, mbean-leak-jira.png
>
>
> # SolrIndexSearcher's register method put the name of searcher, but 
> SolrCore's closeSearcher method remove name of currentSearcher on 
> infoRegistry.
> # SolrIndexSearcher's register method put the name of cache, but 
> SolrIndexSearcher's close do not remove the name of cache.
> so, there maybe lost some memory leak.



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

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

Reply via email to