Re: SolrCore has a large number of SolrIndexSearchers retained in "infoRegistry"

2010-07-20 Thread skommuri

Hi,

I was wondering if anyone has found any resolution to this email thread?

Thank you,
Siva Kommuri
-- 
View this message in context: 
http://lucene.472066.n3.nabble.com/SolrCore-has-a-large-number-of-SolrIndexSearchers-retained-in-infoRegistry-tp483900p982700.html
Sent from the Solr - User mailing list archive at Nabble.com.


Re: SolrCore has a large number of SolrIndexSearchers retained in "infoRegistry"

2010-07-27 Thread skommuri

Thank you very much Hoss for the reply.

I am using the embedded mode (SolrServer). I am not explicitly accessing
SolrIndexSearcher. I am explicitly closing the SolrCore after the request
has been processed.

Although I did notice that I am using SolrQueryRequest object and is not
explicitly getting closed. I will test that one out and will let you know.
Thanks again!


-- 
View this message in context: 
http://lucene.472066.n3.nabble.com/SolrCore-has-a-large-number-of-SolrIndexSearchers-retained-in-infoRegistry-tp483900p1000472.html
Sent from the Solr - User mailing list archive at Nabble.com.


Re: SolrCore has a large number of SolrIndexSearchers retained in "infoRegistry"

2010-07-28 Thread skommuri

Hi,

It didn't seem like it improved the situation. The same exception stack
traces are found. 

I have explicitly defined the index readers to be reopened by specifying in
the solrconfig.xml

The exception occurs when the remote cores are being searched. I am
attaching the exceptions in a text file for reference. 
http://lucene.472066.n3.nabble.com/file/n1002926/solrexceptions.txt
solrexceptions.txt 

Couple of notes:

1. QueryComponent#process
 Is requesting for a SolrIndexSearcher twice by calling
SolrQueryRequest#getSearcher() but is never being closed. I see several
instances where getSearcher is being called but is never being properly
closed - performing a quick call heirarchy of SolrQueryRequest#getSearcher()
and SolrQueryRequest#close() will illustrate this point.

2. It may be the case that this exception was never encountered because
typical deployments are not heavily using Distributed Search across multiple
Solr Cores and/or it's a small memory leak and so never noticed?

-- 
View this message in context: 
http://lucene.472066.n3.nabble.com/SolrCore-has-a-large-number-of-SolrIndexSearchers-retained-in-infoRegistry-tp483900p1002926.html
Sent from the Solr - User mailing list archive at Nabble.com.