Thank you, I will give that a shot.
Zarni
I think this is the way to go. When trying to minimize latency, there are two
statistics to pay particular attention to on your #searchers#.
1> What is the warmup time for your caches?
2> What is your polling interval?
Make sure your polling interval is, say, at least three times longer than
your
Thank you this is something that I wanted to hear. I knew the design was
most likely flawed because I have never done Solr or any kind of full text
searching, but needed an unbiased opinion. I think that if I were to tune
the configs and pay close attention to the logs with lots of performance
te
I really wouldn't go there, it sounds like there are endless
opportunities for errors!
How "real-time" is "real-time"? Could you fix this entirely
by
1> adjusting expectations for, say, 5 minutes.
2> adjusting your commit (on the master) and poll (on the slave) appropriately?
Best
Erick
On Thu,
Hi,
I am designing my indexes to have 1 write-only master core, 2 read-only
slave cores. That means the read-only cores will only have snapshots pulled
from the master and will not have near real time changes. I was thinking
about adding a hybrid read and write master core that will have the mos
