Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-14477

The check of num_tokens against the length of inital_token in the yaml triggers unexpectedly

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Review In Progress
    • Priority: Low
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Local/Config
    • Labels:
      None
    • Severity:
      Low

      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

        Attachments

          Activity

            People

            • Assignee:
              VincentWhite Vincent White
              Reporter:
              VincentWhite Vincent White
              Authors:
              Vincent White
              Reviewers:
              Michael Semb Wever
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: