That should be fine (but apparently isn't), as long as you don't have some very slow machine or if your caches are are large and configured to copy a lot of data on commit.
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Jon Drukman <jdruk...@gmail.com> > To: solr-user@lucene.apache.org > Sent: Friday, January 30, 2009 4:54:06 PM > Subject: Re: exceeded limit of maxWarmingSearchers > > Yonik Seeley wrote: > > I'd advise setting it to a very low limit (like 2) and committing less > > often. Once you get too many overlapping searchers, things will slow > > to a crawl and that will just cause more to pile up. > > > > The root cause is simply too many commits in conjunction with warming > > too long. If you are using a dev version of Solr 1.4, you might try > > commitWithin instead of explicit commits. (see SOLR-793) Depending > > how long warming takes, you may want to lower autowarm counts. > > right now we commit on every update, but that's probably not more than once > every few minutes. should i back it off? > > -jsd-
