[
https://issues.apache.org/jira/browse/CASSANDRA-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010205#comment-14010205
]
Albert P Tobey commented on CASSANDRA-7306:
-------------------------------------------
One real use case is branch locations with local clusters that get replicated
to a central datacenter for analytics. The central cluster has no authority to
open ports or create VPNs in the plants, but it can open ports on the inbound
side. In this situation, the easiest thing to do is to open the inbound ports
to the central cluster and use TLS. The spokes obviously cannot communicate
with each other, but they can push data to the hub. This kind of scenario is
common in retail and manufacturing. Basically, it's useful anywhere there is
hub-and-spoke topology where bidirectional communication is
impossible/intermittent.
Another common problem is NAT traversal where VPN is not available. If there is
no requirement for bi-directional replication, it gets a lot easier to deal
with NAT since the spoke/leaf clusters can connect outbound through NAT into a
centralized cluster. Generating all the firewall rules for such an setup is a
lot of work and prone to error. If only one side needs to modify firewall
policy, it's a lot easier to get right and troubleshoot.
> 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)
