[CASSANDRA-14477] The check of num_tokens against the length of inital_token in the yaml triggers unexpectedly

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 3.0.23, 3.11.9, 4.0-beta4, 4.0
• Component/s: Local/Config
• Severity: Low
• Since Version: 3.0.6

Source Control Link

https://github.com/apache/cassandra/commit/8ef5a886312e20f09cd4b0358c71018908341796

Test and Documentation Plan

CI

• Assignee: Stefan Miklosovic
• Reporter: Vincent White

Authors

Stefan Miklosovic

Reviewers

Michael Semb Wever

• Created: 30/May/18 07:12
• Updated: 18/Nov/20 21:10
• Resolved: 18/Nov/20 12:34

Description

In CASSANDRA-10120 we added a check that compares num_tokens against the number of tokens supplied in the yaml via initial_token. From my reading of CASSANDRA-10120 it was to prevent cassandra starting if the yaml contained contradictory values for num_tokens and initial_tokens which should help prevent misconfiguration via human error. The current behaviour appears to differ slightly in that it performs this comparison regardless of whether num_tokens is included in the yaml or not. Below are proposed patches to only perform the check if both options are present in the yaml.

Branch
3.0.x
3.x

Issue Links

• relates to: CASSANDRA-10120 When specifying both num_tokens and initial_token, error out if the numbers don't match