[
https://issues.apache.org/jira/browse/CASSANDRA-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13154898#comment-13154898
]
Chris Goffinet commented on CASSANDRA-3483:
-------------------------------------------
Jonathan,
You are correct. Sylvain's proposal does satisfy this ticket. It doesn't solve
the case of (2) where if you want to add lots of nodes in an existing DC, and
you know the tokens they should be at, and want to join them all at once.
Our use case is, we actually add 60-100 nodes in one big capacity add. We would
like to avoid the 120 second per node time frame. It's not a deal breaker
though. We actually realized though if we are adding that many nodes to our
cluster, with a large cluster already, we need to rebalance heavily anyway.
Peter is almost done with the 'rebuild' patch, I'm assigning him to this
ticket.
Our next big focus is improving the rebalancing of a cluster. We have a very
large cluster and after adding 100 nodes every month or so, this becomes
painful. Almost all of our nodes have over 600GB+ each. We have an application
that will require us to be rebalancing at all times to reduce our hot spots.
> 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
