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:10:42 UTC

[jira] [Updated] (CASSANDRA-13080) Use new token allocation for non bootstrap case as well.

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

Aleksey Yeschenko updated CASSANDRA-13080:
------------------------------------------
    Fix Version/s:     (was: 3.12)
                   4.0

> Use new token allocation for non bootstrap case as well.
> --------------------------------------------------------
>
>                 Key: CASSANDRA-13080
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13080
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Dikang Gu
>            Assignee: Dikang Gu
>             Fix For: 4.0
>
>
> There are couple reasons I think we should use the new token allocation for non bootstrap case as well.
> 1. In some cases, We want to bring up nodes, but do not need to stream any data to the new nodes. So we want to allocate correct tokens, and skip the JOIN state, which should avoid triggering pending range calculation on other nodes as well. On use case is when we bring up a new DC.
> 2. We can unify the token allocation code path for both bootstrap and non-bootstrap use case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)