[
https://issues.apache.org/jira/browse/SOLR-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198657#comment-14198657
]
Shalin Shekhar Mangar commented on SOLR-2927:
---------------------------------------------
{quote} I synced the trunk code and have some failures.
I don't know how to check for trunk status other that rebuilding it (I did not
find an url where we can check for trunk status)
{quote}
What failures have you seen?
bq. I wonder if it would be better to wait for searcherExecutor shutdown sooner
than later because this thread can keep on doing some work whereas we are
supposed to close the core.
Once the searcherExecutor is shutdown, there won't be any searcher thread doing
any work (including warming). The on deck searcher is also closed before we
clear the infoRegistry.
> 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
