cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7306) Support "edge dcs" with more flexible gossip
Date Mon, 02 Nov 2015 05:58:27 GMT


Jeff Jirsa commented on CASSANDRA-7306:

This ticket title mentions "more flexible gossip" -  does this carry into requests/CL as well?
What's the desired/expected behavior if a KS uses NTS to have rf=3 in dcs {a,b,c}, but hosts
in dc=b are set not to gossip with hosts in dc=c, and vice versa? CL=ALL fails, CL=QUORUM
fills with a+b, and writes just assume all nodes in c are down? Or should it be smart enough
to know that c is disconnected, and not count hosts in c towards quorum/ALL ? 

> Support "edge dcs" with more flexible gossip
> --------------------------------------------
>                 Key: CASSANDRA-7306
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            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

View raw message