I suppose you are still losing some performance on the replicated box since it needs to use some resources to warm the cache. It would be nice if a warmed cache could be replicated from the master though perhaps that's not practical. Chris is right though: The newly updated index created by a commit is not seen by users until it has been warmed, at which point it is atomically swapped.
-Kallin Nagelberg -----Original Message----- From: Chris Hostetter [mailto:hossman_luc...@fucit.org] Sent: Wednesday, May 19, 2010 2:38 PM To: solr-user@lucene.apache.org Subject: Re: disable caches in real time : I've always undestand that if you do a commit (replication does it), a new : searcher is open, and you lose performance (queries per second) while the : caches are regenerated. I think i don't explain correctly my situation not if you configure your caches with autowarming -- then solr will warm up the new caches (on the new index) while the old index still serves requests -- this is all manged for you by the SolrCore, no need for core swapping. -Hoss
