[
https://issues.apache.org/jira/browse/SOLR-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195169#comment-14195169
]
Shalin Shekhar Mangar commented on SOLR-2927:
---------------------------------------------
Thanks for pinging me Michael. This issue had been forgotten.
I now understand the bug and I am able to reproduce it locally. I started with
Cyrille's patch which introduced an exception in the SolrCore constructor and I
added logging of all items which are added to JMX and all the items that are
removed on close after the exception. With a little bit of awk and sort, I have
this list of mbeans which are leaked:
{code}
documentCache
fieldValueCache
filterCache
mlt
perSegFilter
query
queryResultCache
searcher
Searcher@778e65f2[techproducts]
{code}
> 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: 4.9, 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: [email protected]
For additional commands, e-mail: [email protected]
