Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 27 May 2014 19:53:02 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12716885.1401220024422.25398.1401220382897@arcas>
In-Reply-To: <JIRA.12716885.1401220024422@arcas>
References: <JIRA.12716885.1401220024422@arcas>
Subject: [jira] [Commented] (CASSANDRA-7306) Support "edge dcs" with more
 flexible gossip
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010192#comment-14010192 ] 

Brandon Williams commented on CASSANDRA-7306:
---------------------------------------------

I get 2), but what do you have in mind exactly for 1)?

> 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)