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

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 3.0.6, 3.6
• Labels: lhf
• Assignee: Roman Pogribnyi
• Reporter: Jeremy Hanna

Authors

Roman Pogribnyi

Reviewers

Sylvain Lebresne

• Created: 18/Aug/15 19:21
• Updated: 17/Nov/20 22:00
• Resolved: 05/Apr/16 14:32

Description

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.

Issue Links

• is related to: CASSANDRA-14477 The check of num_tokens against the length of inital_token in the yaml triggers unexpectedly