[
https://issues.apache.org/jira/browse/CASSANDRA-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Schuller updated CASSANDRA-3483:
--------------------------------------
Attachment: CASSANDRA-3483-0.8-prelim.txt
Here is a patch rebased against 0.8 for cursory review. I do not expect this to
go into 0.8, and in fact I have not tested this patch other than build against
vanilla 0.8 (the original patch is tested, but against our internal 0.8).
If there are no concerns with the overall implementation, I'll submit a rebased
version for 1.0/trunk.
There are two components of the change:
* Breaking out the streaming part of BootStrapper into a separate
RangeStreamer. Change BootStrapper to use that.
* Implement the rebuild command on top of RangeStreamer.
There are two ways to invoke rebuild:
{code}
nodetool rebuild
nodetool rebuild nameofdc
{code}
The first form streams from nearest endpoints, while the latter streams from
nearest endpoints in the specified data center.
> Support bringing up a new datacenter to existing cluster without repair
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-3483
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3483
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.0.2
> Reporter: Chris Goffinet
> Assignee: Peter Schuller
> Attachments: CASSANDRA-3483-0.8-prelim.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 repair.
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
