You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2016/02/12 14:51:18 UTC

[jira] [Updated] (CASSANDRA-10120) When specifying both num_tokens and initial_token, error out if the numbers don't match

     [ https://issues.apache.org/jira/browse/CASSANDRA-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne updated CASSANDRA-10120:
-----------------------------------------
    Assignee: Roman Pogribnyi

> When specifying both num_tokens and initial_token, error out if the numbers don't match
> ---------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10120
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10120
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jeremy Hanna
>            Assignee: Roman Pogribnyi
>            Priority: Minor
>              Labels: lhf
>             Fix For: 3.x
>
>         Attachments: 10120-3.0.txt
>
>
> Right now if both initial_token and num_tokens are specified, initial_token is used.  As something to not trip people up, it would be nice to do a basic error check.  If both are specified, we should make sure they match.  That is, if they have one initial token and num_tokens of 256, it should error out on startup and alert the user of the configuration.  It's better to fail fast than bootstrap with only one token.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)