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

ReplicationAwareTokenAllocator should block bootstrap if no replication number is set

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Patch Available
    • Priority: Low
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Local/Config
    • Labels:
      None
    • Severity:
      Low

      Description

      We're using ReplicationAwareTokenAllocator. When bootstrapping a new DC, the tokens are not well distributed. The problem is because the replication number is not set for the new DC before the bootstrap.
      I would suggest blocking the bootstrap if replication number is not set. It's unsafe to assume the default replicas is 1. Which also causes the following invalid stats:

      WARN  [main] 2018-06-29 17:30:55,696 TokenAllocation.java:69 - Replicated node load in datacenter before allocation max NaN min NaN stddev NaN
      WARN  [main] 2018-06-29 17:30:55,696 TokenAllocation.java:70 - Replicated node load in datacenter after allocation max NaN min NaN stddev NaN
      

        Attachments

          Activity

            People

            • Assignee:
              jay.zhuang Jay Zhuang
              Reporter:
              jay.zhuang Jay Zhuang
              Authors:
              Jay Zhuang
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: