What William said was the original motivation to sync all slaves to poll
approximately at the same time.
On Tue, Mar 20, 2012 at 10:38 PM, William Bell wrote:
> For our use case this is a no-no. When the index is updated, we need
> all indexes to be updated at the same time.
>
> We put all index
For our use case this is a no-no. When the index is updated, we need
all indexes to be updated at the same time.
We put all indexes (slaves) behind a load balancer and the user would
expect the same results from page to page.
On Tue, Mar 20, 2012 at 5:36 AM, Eric Pugh
wrote:
> I am playing with
I am playing with an index that is sharded many times, between 64 and 128. One
thing I noticed is that with replication set to happen every 5 minutes, it
means that each slave hits the master at the same moment asking for updates:
:00:00, :05:00, :10:00, :15:00 etc. Replication takes very li