[
https://issues.apache.org/jira/browse/CASSANDRA-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010210#comment-14010210
]
Albert P Tobey commented on CASSANDRA-7306:
-------------------------------------------
Another angle: small edge clusters for low latency writes in many regions that
push to a central warehouse for analytics. Think GSLB -> HTTP -> Cassandra all
over the world with regional clusters replicated to us-west-2 where the data is
crunched with Spark or Hadoop. This is basically the MySQL read-replica flipped
on its head with 0-read write-replicas going into a read-heavy warehouse. The
central cluster could be 100's of nodes while edge clusters are in the 5-10
range.
> Support "edge dcs" with more flexible gossip
> --------------------------------------------
>
> Key: CASSANDRA-7306
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7306
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Tupshin Harper
> Labels: ponies
>
> As Cassandra clusters get bigger and bigger, and their topology becomes more
> complex, there is more and more need for a notion of "hub" and "spoke"
> datacenters.
> One of the big obstacles to supporting hundreds (or thousands) of remote dcs,
> is the assumption that all dcs need to talk to each other (and be connected
> all the time).
> This ticket is a vague placeholder with the goals of achieving:
> 1) better behavioral support for occasionally disconnected datacenters
> 2) explicit support for custom dc to dc routing. A simple approach would be
> an optional per-dc annotation of which other DCs that DC could gossip with.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
