cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3483) Support bringing up a new datacenter to existing cluster without repair
Date Mon, 21 Nov 2011 21:04:52 GMT

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

Jonathan Ellis commented on CASSANDRA-3483:
-------------------------------------------

So, am I understanding correctly that we're talking about two different scenarios?

- Add new DC without repair
- Add many nodes to existing DC without RING_DELAY in between

I think Sylvain's proposal addresses the first nicely.  So what I need help with is understanding
what problem you're trying to solve with the second part.  Dealing with overlapping ranges
in node movement basically requires a rewrite of that subsystem (CASSANDRA-2434).  But I suspect
there is a "good enough" solution that we could find if I understood better what your pain
point is here.
                
> 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

        

Mime
View raw message