In our setup, snapshooter is triggered on optimize, not commit. We can commit all we want on the master without making a snapshot. That only happens when we optimize.
The new Searcher is the biggest performance impact for us. We don't have that many documents (~250K), so copying an entire index is not a big deal. wunder On 4/25/08 8:28 AM, "Otis Gospodnetic" <[EMAIL PROTECTED]> wrote: > Don't think so. But you reindex on the master and query on the slave. If > your concern is that the index will be sent to the search slave while you are > still reindexing, just don't commit until you are done. > > > Otis > -- > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > > ----- Original Message ---- >> From: Jonathan Ariel <[EMAIL PROTECTED]> >> To: solr-user@lucene.apache.org >> Sent: Friday, April 25, 2008 10:05:55 AM >> Subject: Reindexing mode for solr >> >> Hi, >> Is there any way to tell solr to load in a kind of reindexing mode, which >> won't open a new searcher after every commit, etc? This is just when you >> don't have it available to query because you just want to reindex all the >> information. >> >> What do you think? >> >> Jonathan >
