[
https://issues.apache.org/jira/browse/CASSANDRA-14551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597961#comment-16597961
]
Jay Zhuang commented on CASSANDRA-14551:
----------------------------------------
Hi [~dikanggu], I just saw your response in the commit:
{quote}
I explicitly made it work with 0 replication factor case in this jira,
CASSANDRA-12983. This change will break the behavior in that situation, right?
{quote}
Yeah, I see your point. I think the suggestion for that (and other use cases)
is using a separate dummy keyspace for {{allocate_tokens_for_keyspace}}, so you
can have more control over token allocation and production keyspace. Default
replication to 1 may not be a right assumption.
> ReplicationAwareTokenAllocator should block bootstrap if no replication
> number is set
> -------------------------------------------------------------------------------------
>
> Key: CASSANDRA-14551
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14551
> Project: Cassandra
> Issue Type: Bug
> Components: Configuration
> Reporter: Jay Zhuang
> Assignee: Jay Zhuang
> Priority: Minor
>
> We're using
> [ReplicationAwareTokenAllocator|https://www.datastax.com/dev/blog/token-allocation-algorithm].
> 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:
> {noformat}
> 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
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
