[jira] [Comment Edited] (CASSANDRA-4641) Make upgrade to vnodes only happen on new installs

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis edited comment on CASSANDRA-4641 at 9/11/12 2:05 AM:
--------------------------------------------------------------------

IMO, num_tokens should act like initial_token: respected on first startup, ignored otherwise.  (This lets us make num_tokens: 256 be the default for new installs, while not touching upgraders [even if they deploy the new cassandra.yaml] until they explicitly ask for it.)
                
      was (Author: jbellis):
    IMO, num_tokens should act like initial_token: respected on startup, ignored otherwise.  (This lets us make num_tokens: 256 be the default for new installs, while not touching upgraders [even if they deploy the new cassandra.yaml] until they explicitly ask for it.)
                  
> Make upgrade to vnodes only happen on new installs
> --------------------------------------------------
>
>                 Key: CASSANDRA-4641
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4641
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Brandon Williams
>            Assignee: Eric Evans
>             Fix For: 1.2.0 beta 1
>
>
> We should make vnodes be the default for new installs, however, just enabling the 'num_tokens' parameter for upgrading is too flimsy.  Instead, we should have a jmx/nodetool operation to do the upgrading.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira