Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Mon, 2 Aug 2010 14:33:47 -0700 (PDT)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: solr-user@lucene.apache.org
Subject: Re: SolrCore has a large number of SolrIndexSearchers retained in
 "infoRegistry"
In-Reply-To: <1280353528035-1002926.post@n3.nabble.com>
Message-ID: <alpine.DEB.1.10.1008021425210.1697@radix.cryptio.net>
References: <B0C15822D6DFAC4586DF221BC7AFE6C4014B84071BCA@vyre-m.vyre.com>
 <17E4B507-153D-4A0B-B428-1C6570E32A94@apache.org>
 <1279663071397-982700.post@n3.nabble.com>
 <alpine.DEB.1.10.1007271215050.1072@radix.cryptio.net>
 <1280260065276-1000472.post@n3.nabble.com>
 <1280353528035-1002926.post@n3.nabble.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: 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.

i believe you missunderstood my point -- i never said code that calls 
SolrQueryRequest#getSearcher needs to call SolrQueryRequest#close ...  i 
said that SolrIndexSearcher methods are ref counted, and that they those 
refrence counts needto be dealt with properly to ensure that the 
SOlrIndexSearchers are closed properly -- the fact that you are using 
embedded solr, and the fact that you are calling SolrCore.execute means 
that you *must* (by defintion) be instnatiating your own instances of 
SolrQueryRequest, which means thta you *must* (by definition) be "getting" 
a SolrIndexSearcher object from some method that requires you to "release" 
that SolrIndexSearcher when you are done.  If you use Solr as a server, it 
takes care of calling SolrQueryRequest.close() for you and it takes care 
of releasing the SolrIndexSearcher assocaited with that SolrQueryRequest 
object.

I realize now that i wasn't explicit in my previous response but there is 
absolutely *no* way that anyone can provide any meaninful assistance to 
you in understanding these errors w/o you showing us *exactly* how you are 
using solr, and what your custom code looksl ike that you have embedded 
solr in -- we need to see how you instantiate your SOlrCore, we need to 
see all of the code involved when you call the execute method, we need to 
see where you get your SolrQueryRequest object from, we need to see where 
you get your SolrIndexSearcher from ... all of it.

As i said: these types of resources leaks are entirely dependent on *how* 
you use the code ... if you were using Solr as a server, we would know 
exactly how the objects are being accessed/released because that code is 
in SOlr -- but when you embedded Solr in custom code we have nothing to go 
on but what you tell us.


-Hoss