You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2017/02/05 16:18:41 UTC

[jira] [Updated] (CASSANDRA-12983) NoReplicationTokenAllocator should work with zero replication factor as well.

     [ https://issues.apache.org/jira/browse/CASSANDRA-12983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-12983:
------------------------------------------
    Fix Version/s:     (was: 3.12)
                   3.11.0

> 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.11.0
>
>
> 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.15#6346)