Thanks for all the information.
I'm not sure how exactly you are measuring/defining replication lag but
if you mean lag in how long until the newly replicated documents are
visible in searches
That is exactly what I wanted to say.
I've attached the cache statistics.
If you are interested
: However, with these modifications we noticed an important replication
I'm not sure how exactly you are measuring/defining replication lag but
if you mean lag in how long until the newly replicated documents are
visible in searches then that _may_ be fairly easy to explain...
: My previous
Thanks for your answer Erick.
For the polling interval, we use 1 second for the small index and 1 minute
for the big one. I'll try to increase it up to 5 minutes and see if it
solve the problem.The issue doesn't occur with the default cache settings
(i.e. cache size=512).
Indeed, we strive for
You polling interval is much too short. 1 second
is probably getting you into resource contention
issues.
A more reasonable interval is on the order of several
minutes. If you really need near real time
searching, consider 4.0 which supports NRT
Best
Erick
On Fri, Aug 31, 2012 at 10:02 AM,
