I'd say: "Make sure you don't commit more frequently than the time it takes for your searcher to warm up", or else you risk searcher overlap and pile-up.
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ________________________________ From: Jon Drukman <jdruk...@gmail.com> To: solr-user@lucene.apache.org Sent: Thursday, February 5, 2009 11:36:13 AM Subject: Re: exceeded limit of maxWarmingSearchers Otis Gospodnetic wrote: > Jon, > > If you can, don't commit on every update and that should help or fully solve > your problem. is there any sort of heuristic or formula i can apply that can tell me when to commit? put it in a cron job and fire it once per hour? there are certain updates that are critical - we store privacy settings on certain data in the doc. if the user says that document 10 is private, we need to have the update reflected immediately. is there any way to have solr block everything until an update is committed? -jsd-
