[CASSANDRA-14551] ReplicationAwareTokenAllocator should block bootstrap if no replication number is set

• Type: Bug
• Status: Patch Available
• Priority: Low
• Resolution: Unresolved
• Component/s: Local/Config
• Severity: Low
• Assignee: Jay Zhuang
• Reporter: Jay Zhuang

Authors

Jay Zhuang

• Created: 30/Jun/18 00:33
• Updated: 16/Apr/19 09:29

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