[
https://issues.apache.org/jira/browse/CASSANDRA-12983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713757#comment-15713757
]
Dikang Gu commented on CASSANDRA-12983:
---------------------------------------
The patch based on trunk.
|[patch |
https://github.com/DikangGu/cassandra/commit/03353c3aacb07ce668f243a058baeee71e882246
]|[unit test |
https://cassci.datastax.com/view/Dev/view/DikangGu/job/DikangGu-CASSANDRA-12983-trunk-testall/
]|[dtest |
https://cassci.datastax.com/view/Dev/view/DikangGu/job/DikangGu-CASSANDRA-12983-trunk-dtest/]|
> NoReplicationTokenAllocator should work with zero replication factor as well.
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-12983
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12983
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Dikang Gu
> Assignee: Dikang Gu
> Fix For: 3.12
>
>
> In our production env, when we expand an existing cluster to a new DC, we are
> doing following steps:
> 1. set replication factor to be 0 for the new DC.
> 2. bootstrap all nodes in the new DC.
> 3. set the replication factor to be 1 and start the rebuild.
> I find the NoReplicationTokenAllocator does not work with replication factor
> 0, and this patch will fix it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
