No, caches are not replicated across slaves. You really have
two choices:
1> use some sort of "sticky" addressing whereby requests
from the same client are sent to the same slave.
2> don't worry about it <G>. Examine your cache stats
to see how often your caches, particularly your
QueryResultCache is utilized. If users aren't
paging into your system, it's probable that your
QueryResultCache is not buying you that much
in the first place. As for the other caches, I usually
work on the assumption that they'll hit a steady
state sometime anyway and you'll get your re-use,
especially if you use you warming queries appropriately.
And all this is moot anyway after any replication, many of
the caches have to be rebuilt. If you have a system that
you can predict what caches will be used, you can always
use warmup queries to make that happen. In particular
look at auto-warming...
Buy propagating caches would be tricky, and I suspect
far more problem than value
Best
Erick
On Tue, Aug 9, 2011 at 7: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.
>
