Oh yes, that is cool. I see from the code now (was reading it incorrectly).
So a Quorum with NTS would give me 3 copies across the cluster, not
necessarily 2 local and 1 remote, but for most parts that would be true
since WAN adds to latency.
Thanks
On Thu, Sep 8, 2011 at 3:40 PM, Jonathan Elli
CL.QUORUM is supported with any replication strategy, not just simple.
Also, Cassandra's optimizing of cross-DC writes only requires that it
know (via a correctly configured Snitch) where each node is located.
It is not affected by replication strategy choice.
On Thu, Sep 8, 2011 at 3:14 PM, Anan
On Thu, Sep 8, 2011 at 4:14 PM, Anand Somani wrote:
> Hi,
>
> Have a requirement, where data is spread across multiple DC for disaster
> recovery. So I would use the NTS, that is clear, but I have some questions
> with this scenario
>
>- I have 2 Data Centers
>- RF - 2 (active DC) , 2 (pa
Hi,
Have a requirement, where data is spread across multiple DC for disaster
recovery. So I would use the NTS, that is clear, but I have some questions
with this scenario
- I have 2 Data Centers
- RF - 2 (active DC) , 2 (passive DC)
- with NTS - Consistency level options are - LOCAL_QUOR
