I haven't done it yet, but when I researched how to make
geo-diverse/failover DCs, I figured I'd have to do something like RF=6,
strategy = {DC1=3, DC2=3}, and LOCAL_QUORUM for reads/writes. This gives
you an "ack" after 2 local nodes do the read/write, but the data eventually
gets distributed to the other DC for a full failover. No "ying-yang", but I
believe accomplishes the same goal?
will
On Fri, Jun 17, 2011 at 2:20 AM, Jonathan Ellis <jbel...@gmail.com> wrote:
> Replication location is determined by the row key, not the location of
> the client that inserted it. (Otherwise, without knowing what DC a
> row was inserted in, you couldn't look it up to read it!)
>
> On Fri, Jun 17, 2011 at 12:20 AM, AJ <a...@dude.podzone.net> wrote:
> > On 6/16/2011 9:45 PM, aaron morton wrote:
> >>>
> >>> But, I'm thinking about using OldNetworkTopStrat.
> >>
> >> NetworkTopologyStrategy is where it's at.
> >
> > Oh yeah? It didn't look like it would serve my requirements. I want 2
> full
> > production geo-diverse data centers with each serving as a failover for
> the
> > other. Random Partitioner. Each dc holds 2 replicas from the local
> clients
> > and 1 replica goes to the other dc. It doesn't look like I can do a
> > ying-yang setup like that with NTS. Am I wrong?
> >
> >> A
> >> -----------------
> >> Aaron Morton
> >> Freelance Cassandra Developer
> >> @aaronmorton
> >> http://www.thelastpickle.com
> >
> >
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com
>
--
Will Oberman
Civic Science, Inc.
3030 Penn Avenue., First Floor
Pittsburgh, PA 15201
(M) 412-480-7835
(E) ober...@civicscience.com
