cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8060) Geography-aware, distributed replication
Date Mon, 15 Dec 2014 23:30:14 GMT


Jeremy Hanna commented on CASSANDRA-8060:

Through gossip and the dynamic snitch, I would think we already have "nearness" information.
 That would make it so you wouldn't need to feed it a topology definition I think.  That could
be the default, and you could optionally override that with your own configuration, perhaps
because of link costs or whatever.

> Geography-aware, distributed replication
> ----------------------------------------
>                 Key: CASSANDRA-8060
>                 URL:
>             Project: Cassandra
>          Issue Type: Wish
>            Reporter: Donald Smith
>            Assignee: Jason Brown
> We have three data centers in the US (CA in California, TX in Texas, and NJ in NJ), two
in Europe (UK  and DE), and two in Asia (JP and CH1).  We do all our writing to CA.  That
represents a bottleneck, since the coordinator nodes in CA are responsible for all the replication
to every data center.
> Far better if we had the option of setting things up so that CA replicated to TX , which
replicated to NJ. NJ is closer to UK, so NJ should be responsible for replicating to UK, which
should replicate to DE.  Etc, etc.
> This could be controlled by the topology file.
> The replication could be organized in a tree-like structure instead of a daisy-chain.
> It would require architectural changes and would have major ramifications for latency
but might be appropriate for some scenarios.

This message was sent by Atlassian JIRA

View raw message