No,
You can't assume that. You have to set a good autoCommit value for your
solrconfig.xml, so you don't run out of memory for no commiting to Solr
often, depending on your enviroment, memory share, doc size and update
frequency.
2009/1/16 Manupriya
>
> Thanks for the information!!
>
> So can I
Thanks for the information!!
So can I safely assume that we will not face any memory issue due to caching
even if we do not send commit that frequently? (If we wont send commit, then
new searcher wont be initialized. So I can assume that the current searcher
will correctly manage cache without an
Shalin is right about cache management, but fot the sake of knowledge,
everytime you sendd a commit to Solr, it will close the old Searcher and
open a new one.
2009/1/16 Shalin Shekhar Mangar
> On Fri, Jan 16, 2009 at 4:17 PM, Manupriya >wrote:
>
> >
> > Hi,
> >
> > We are using Solr as a stand
On Fri, Jan 16, 2009 at 4:17 PM, Manupriya wrote:
>
> Hi,
>
> We are using Solr as a standalone server. And our web application sends a
> HTTP request for searching. We receive JSON result back and use the result.
>
> I had initailly asked about Searher
> (http://www.nabble.com/What-do-we-mean-by-
