lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "FAQ" by HossMan
Date Wed, 02 Dec 2009 20:26:34 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "FAQ" page has been changed by HossMan.
The comment on this change is: exceeded limit of maxWarmingSearchers.
http://wiki.apache.org/solr/FAQ?action=diff&rev1=62&rev2=63

--------------------------------------------------

  
  The most common cause is from using a version of Solr+Lucene that is older then the version
used to create that index.
  
+ == What does "exceeded limit of maxWarmingSearchers=X" mean? ==
+ 
+ Whenever a commit happens in Solr, a new "searcher" (with new caches) is opened, "warmed"
up according to your SolrConfigXml settings, and then put in place.  The previous searcher
is not closed until the "warming" search is ready.  If multiple commits happen in rapid succession
-- before the warming searcher from first commit has enough time to warm up, then there can
be multiple searchers all competeing for resources at the same time, even htough one of them
will be thrown away as soon as the next one is ready.
+ 
+ maxWarmingSearchers is a setting in SolrConfigXml that helps you put a safety valve on the
number of overlapping warming searchers that can exist at one time.  If you see this error
it means Solr prevented a commit from resulting an a new searcher being opened because there
were already X warming searchers open.
+ 
+ If you encounter this error a lot, you can (in theory) increase the number in your maxWarmingSearchers,
but that is risky to do unless you are confident you have the system resources (RAM, CPU,
etc...) to do it safely.  A more correct way to deal with the situation is to reduce how frequently
you send commits.
+ 
+ If you only encounter this error infrequently because of fluke situations, you'll probably
be ok just ignoring it.
+ 
  = Searching =
  
  == How to make the search use AND semantics by default rather than OR? ==

Mime
View raw message