cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3483) Support bringing up a new datacenter to existing cluster without repair
Date Mon, 30 Jan 2012 14:06:11 GMT


Jonathan Ellis commented on CASSANDRA-3483:

bq. Overall, I fully agree this is a problem that we should fix someone, but I'm not sure
the FetchConsistencyLevel is the right solution and even if it is it's a complicated enough
problem that it's worth it's own 

This is CASSANDRA-2434 isn't it?
> Support bringing up a new datacenter to existing cluster without repair
> -----------------------------------------------------------------------
>                 Key: CASSANDRA-3483
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Chris Goffinet
>            Assignee: Peter Schuller
>             Fix For: 1.1
>         Attachments: 3483-v3.patch, CASSANDRA-3483-0.8-prelim.txt, CASSANDRA-3483-1.0.txt,
CASSANDRA-3483-trunk-noredesign.txt, CASSANDRA-3483-trunk-rebase2.txt, CASSANDRA-3483-trunk-refactored-v1.txt,
> Was talking to Brandon in irc, and we ran into a case where we want to bring up a new
DC to an existing cluster. He suggested from jbellis the way to do it currently was set strategy
options of dc2:0, then add the nodes. After the nodes are up, change the RF of dc2, and run
> I'd like to avoid a repair as it runs AES and is a bit more intense than how bootstrap
works currently by just streaming ranges from the SSTables. Would it be possible to improve
this functionality (adding a new DC to existing cluster) than the proposed method? We'd be
happy to do a patch if we got some input on the best way to go about it.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message