cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Goffinet (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (CASSANDRA-3483) Support bringing up a new datacenter to existing cluster without repair
Date Thu, 17 Nov 2011 06:32:51 GMT

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

Chris Goffinet edited comment on CASSANDRA-3483 at 11/17/11 6:31 AM:
---------------------------------------------------------------------

Sorry, I had to re-read what Sylvain said for it to 'click'. So the process he proposes is
as follows with RF of 3:

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

this would handle the writes part.

i was kinda hoping though that we could modify the gossip state because I could very well
see this playing into the case where you weren't adding DCs but wanted to add lots of nodes
(60-100 like we do currently) ... and wanted to have them all added to existing DC.. having
the bootstrap defined that way, would allow us to bootstrap nodes as we please in existing
DCs, bring them all to the ring at once to have a consistent state without taking on traffic
until they transitioned states (joining/normal). Where as this proposal wouldn't be able to
satisfy that use case.


                
      was (Author: lenn0x):
    Sorry, I had to re-read what Sylvain said for it to 'click'. So the process he proposes
is as follows with RF of 3:

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

this would handle the writes part.

i was kinda hoping though that we could modify the gossip state because I could very well
see this playing into the case where you weren't adding DCs but wanted to add lots of nodes
(60-100 like we do currently) ... and wanted to have them all added to existing DC.. having
the bootstrap defined that way, would allow us to bootstrap nodes as we please in existing
DCs, bring them to ring all at once to have a consistent state without taking on traffic until
they changed states. Where as this proposal wouldn't be able to satisfy that use case.


                  
> 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