cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4641) Make upgrade to vnodes only happen on new installs
Date Mon, 10 Sep 2012 15:56:08 GMT


Sylvain Lebresne commented on CASSANDRA-4641:

I'm asking because if we do the 'num_tokens is only respected on first startup, it means people
that upgrade and later bootstrap a node would end up with the new node have multiple tokens
unless they explicitly set num_tokens. In other words, that would still be pretty confusing
for upgraders.

Imo, vnodes should be opt-in for upgraders in 1.2 and having new nodes get multiple tokens
by default does not accomplish that.  
> Make upgrade to vnodes only happen on new installs
> --------------------------------------------------
>                 Key: CASSANDRA-4641
>                 URL:
>             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:

View raw message