Consider putting a cache (memcached, redis, etc) *in front* of your solr slaves. Just make sure to update it when replication occurs.
didier On Tue, Aug 9, 2011 at 6:07 PM, arian487 <akarb...@tagged.com> wrote: > I'm wondering if the caches on all the slaves are replicated across (such as > queryResultCache). That is to say, if I hit one of my slaves and cache a > result, and I make a search later and that search happens to hit a different > slave, will that first cached result be available for use? > > This is pretty important because I'm going to have a lot of slaves and if > this isn't done, then I'd have a high chance of running a lot uncached > queries. > > Thanks :) > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Cache-replication-tp3240708p3240708.html > Sent from the Solr - User mailing list archive at Nabble.com. >
