cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Pogribnyi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10120) When specifying both num_tokens and initial_token, error out if the numbers don't match
Date Sun, 03 Apr 2016 19:51:25 GMT

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

Roman Pogribnyi updated CASSANDRA-10120:
----------------------------------------
    Attachment: 10120-3.0.txt

Updated patch to check whether size(initial_token) == num_tokens

> 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, 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)

Mime
View raw message