cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dikang Gu (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-13080) Use new token allocation for non bootstrap case as well.
Date Tue, 03 Jan 2017 18:41:58 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795791#comment-15795791
] 

Dikang Gu edited comment on CASSANDRA-13080 at 1/3/17 6:41 PM:
---------------------------------------------------------------

some dtests failed, should because it does not create the keyspace before bootstrapping more
nodes, I will fix them before committing this.

https://cassci.datastax.com/view/Dev/view/DikangGu/job/DikangGu-CASSANDRA-13080-trunk-dtest/5/testReport/


was (Author: dikanggu):
some dtests failed, should because it does not create the keyspace before bootstrapping more
nodes, I will fix them before committing this.

> 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: 3.12
>
>
> 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.4#6332)

Mime
View raw message