The commit after each one may be hurting you.

I believe that a new searcher is created after each commit. That searcher then 
runs through its warm up, which can be costly depending on your warming 
settings. Even if it's not overly costly, creating another one while the first 
one is running makes both of them run just a bit slower. Then creating a third 
exacerbates it, etc. If you are commiting faster then it can warm, you will get 
the pile-up of searchers you are seeing. And the more that pile up, the longer 
it takes each one to finish up.

I would suggest trying to group those 4-10 documents into a single update job 
and doing a single commit. That way only 1 searcher is created per 4 minute 
window.

Also (sorry I forgot this earlier) you can see how long your searcher is 
spending warming up by looking at the stats page under the admin. 
(/admin/stats.jsp) There is timing information on how long it took for the 
searcher and caches to warm up.

-Todd Feak

-----Original Message-----
From: dudes dudes [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 01, 2008 1:46 PM
To: solr-user@lucene.apache.org
Subject: RE: maxWarmingSearchers




> Subject: RE: maxWarmingSearchers
> Date: Mon, 1 Dec 2008 13:35:53 -0800
> From: [EMAIL PROTECTED]
> To: solr-user@lucene.apache.org
> 
> Ok sounds reasonable. When you index/update those 4-10 documents, are
> you doing a single commit? OR are you doing a commit after each one?

well, commits after each one..

> How big is your index? How big are your documents? Ballpark figures are
> ok.

more than couple of MBs 

one final piece of information: I only have 2 G of RAM on that machine( linux 
on VMware environment ) and increased the memory of tomcat to 1 G

thanks


> 
> -ToddFeak
> 
> -----Original Message-----
> From: dudes dudes [mailto:[EMAIL PROTECTED] 
> Sent: Monday, December 01, 2008 1:24 PM
> To: solr-user@lucene.apache.org
> Subject: RE: maxWarmingSearchers
> 
> 
> Hi ToddFeak, 
> 
> thanks for your response... 
> 
> solr version is 1.3. Roughly about every 4 minutes there are
> indexing/updaing of 4 to 10 documents ....that is from multiple clients
> to one master server... 
> 
> It is also worth  mentioning that I have 
> 
> 
>       
>       
>       
>       postCommit uncommented under solrconfig ... QueryCache and
> FilterCache settings are left as default.... 
> 
> thanks
> ak
> 
> 
> 
> 
> 
> 
> > Subject: RE: maxWarmingSearchers
> > Date: Mon, 1 Dec 2008 13:13:15 -0800
> > From: [EMAIL PROTECTED]
> > To: solr-user@lucene.apache.org
> > 
> > Probably going to need a bit more information.
> > 
> > Such as: 
> > What version of Solr and a little info on doc count, index size, etc.
> > How often are you sending updates to your Master? 
> > How often are you committing? 
> > What are your QueryCache and FilterCache settings for autowarm?
> > Do you have queries set up for newSearcher and firstSearcher?
> > 
> > To start looking for your problem, you usually get a pile up of
> > searchers if you are committing too fast, and/or the warming of new
> > searchers is taking an extraordinary long time. If is happening in a
> > repeatable fashion, increasing the number of warming searchers
> probably
> > won't fix the issue, just delay it.
> > 
> > -ToddFeak
> > 
> > -----Original Message-----
> > From: dudes dudes [mailto:[EMAIL PROTECTED] 
> > Sent: Monday, December 01, 2008 12:13 PM
> > To: solr-user@lucene.apache.org
> > Subject: maxWarmingSearchers
> > 
> > 
> > Hello all, 
> > 
> > I'm having this issue and I hope I get some help.. :)
> > 
> > This following happens quite often ... even though searching  and
> > indexing are on a safe side... 
> > 
> > SolrException: HTTP code=503, reason=Error opening new searcher.
> > exceeded
> > 
> > limit of maxWarmingSearchers=4, try again later.
> > 
> > I have increased the value of  maxWarmingSearchers to 8 and I still
> > experience the same problem.... 
> > 
> > This issue is happening to the master solr server ,,,, changing
> > maxWarmingSearchers  to higher value would help overcoming this issue
> ?
> > or I should consider some other points ?
> > 
> > Another question is ? from your experience, do you think such error
> > introduces server crash ? 
> > 
> > 
> > thanks for your time..
> > ak 
> > 
> > 
> > 
> > _________________________________________________________________
> > Get a bird's eye view of the world with Multimap
> > http://clk.atdmt.com/GBL/go/115454059/direct/01/
> 
> _________________________________________________________________
> Get Windows Live Messenger on your Mobile
> http://clk.atdmt.com/UKM/go/msnnkmgl0010000001ukm/direct/01/

_________________________________________________________________
Imagine a life without walls.  See the possibilities. 
http://clk.atdmt.com/UKM/go/122465943/direct/01/

Reply via email to