cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-7411) Node enables vnodes when bounced
Date Tue, 17 Jun 2014 18:19:17 GMT


Philip Thompson updated CASSANDRA-7411:

    Reproduced In: 2.1 rc1, 2.0.8  (was: 2.0.8, 2.1 rc1)
       Attachment: system.log

> Node enables vnodes when bounced
> --------------------------------
>                 Key: CASSANDRA-7411
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: OSX 9
>            Reporter: Philip Thompson
>         Attachments: system.log
> According to cassandra.yaml, in the information for the num_tokens setting, "Specifying
initial_token will override this setting." So if exactly one initial token is set, then vnodes
are disabled, regardless of if or what num_tokens are set to. This behavior is inconsistent
when a node is started, versus if it has been bounced.
> From a fresh checkout of C*, if I build, then edit cassandra.yaml so that:
> num_tokens: 256
> initial_token: -9223372036854775808
> then run bin/cassandra, C* will start correctly. I can run bin/nodetool ring and see
that the node has exactly one token and it is what I set in initial_token. If I gracefully
shutdown C*, then restart the node, running bin/nodetool ring shows that the node now has
vnodes enabled and has 256 tokens.
> I have been able to reproduce this locally on OSX using 2.0.8, 2.1 rc1, and trunk. I
have not yet tested in Linux or Windows to see if it occurs there.

This message was sent by Atlassian JIRA

View raw message