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

    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

        Issue Links

          Activity

            People

              stefan.miklosovic Stefan Miklosovic
              VincentWhite Vincent White
              Stefan Miklosovic
              Michael Semb Wever
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 1h 10m
                  1h 10m