cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3483) Support bringing up a new datacenter to existing cluster without repair
Date Mon, 05 Dec 2011 16:10:43 GMT


Jeremiah Jordan commented on CASSANDRA-3483:

Once this option is in, is this the procedure for running rebuild (with 4 changed to 'rebuild

1. strategy options dc2:0
2. bring up new nodes in dc2 with auto_bootstrap off and token set
3. set strategy options dc2:3
4. run 'rebuild' on each node in dc2

Do we need to stagger issuing the rebuild commands or can they be run all at once?

> Support bringing up a new datacenter to existing cluster without repair
> -----------------------------------------------------------------------
>                 Key: CASSANDRA-3483
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.0.2
>            Reporter: Chris Goffinet
>            Assignee: Peter Schuller
>         Attachments: CASSANDRA-3483-0.8-prelim.txt, CASSANDRA-3483-1.0.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