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

Sylvain Lebresne commented on CASSANDRA-3483:
---------------------------------------------

So you're proposing to add support for bootstrapping multiple nodes together. 
I'm not against that, it would be nice and that would give you 90% of what this 
ticket is about (you'd have to add the ability to multi-boostrap *and* add a 
DC/augment the replication faction at the same time). But it is orders of 
magnitude more complicated than what I'm suggesting. Which is not a problem in 
itself given it's a broader solution, but it means we'll have multi-node 
boostrap at best for 1.1, while I'm pretty sure I can get the 'rebuild' command 
wrote in like an hour (and I see no reason why it couldn't be put in the 1.0 
series).


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

        

Reply via email to