I saw this awhile back: With requests possibly coming in from either US region, we need to make > sure that the replication of data happens within an acceptable time > threshold. This lead us to perform an experiment where we wrote 1 million > records in one region of a multi-region cluster. We then initiated a read, > 500ms later, in the other region, of the records that were just written in > the initial region, while keeping a production level of load on the > cluster. All records were successfully read.
from http://techblog.netflix.com/2013/12/active-active-for-multi-regional.html On Tue, Jul 29, 2014 at 5:53 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Tue, Jul 29, 2014 at 3:15 PM, Rahul Neelakantan <ra...@rahul.be> wrote: > >> Does anyone know of a way to measure/monitor WAN replication latency for >> Cassandra? > > > No. [1] > > =Rob > > [1] There are ways to do something like this task, but you probably don't > actually want to do them. Trying to do them suggests that you are relying > on WAN replication timing for your application, which is something you > almost certainly do not want to do. Why do you believe you have this > requirement? >
