[
https://issues.apache.org/jira/browse/CASSANDRA-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010231#comment-14010231
]
Matt Kennedy commented on CASSANDRA-7306:
-----------------------------------------
It should be noted that we can do some of this today by defining keyspaces that
only have # of replicas > 0 in some data centers. But, gossip still needs to
function over all the nodes.
Hub & Spoke functionality is useful in situations where the spokes are
geographically dispersed, potentially in areas with less than ideal network
connections. Local clients should be able to read/write locally relevant data
on small scale clusters and make progress even when completely disconnected
from the mothership without having to worry about replicating back a lot of
data from unrelated DCs, or having to be networked to DCs halfway across the
planet just to gossip between nodes that are otherwise unrelated.
> 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)
