OK. But SOLR has built-in caching. Do you not like the caching? What so
you think we should change to the SOLR cache?
Bill
On 8/10/11 9:16 AM, "didier deshommes" wrote:
>Consider putting a cache (memcached, redis, etc) *in front* of your
>solr slaves. Just make sure to update it when replicati
Thanks for the advice paul, but post processing is a must for me given the
nature of my application. I haven't had problems yet though.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Cache-replication-tp3240708p3244202.html
Sent from the Solr - User mailing list archive at
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 wrote:
> I'm wondering if the caches on all the slaves are replicated across (such as
> queryResultCache). That i
Arian,
I've been doing results post-processing in some versions of the ActiveMath
server and it has been the wrong choice as much as possible.
Maybe this is not what you do, but the biggest flaw was that the
post-processing was eliminating or adding results (for insiders of ActiveMath:
converti
Thanks for the informative response. I'll consider using the 'sticky'
addressing as you suggested. The reason cache is so important for me is
because I'm actually doing more processing after the query component to come
up with my query result and I want to avoid that processing as much as
possibl
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 . Examine your cache stats
to see how often your caches, particularly your
Query
