Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 5 Jan 2017 20:23:58 +0000 (UTC)
From: "Dikang Gu (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13030771.1482868628000.654339.1483647838895@Atlassian.JIRA>
In-Reply-To: <JIRA.13030771.1482868628000@Atlassian.JIRA>
References: <JIRA.13030771.1482868628000@Atlassian.JIRA> <JIRA.13030771.1482868628409@arcas>
Subject: [jira] [Updated] (CASSANDRA-13080) Use new token allocation for non
 bootstrap case as well.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 05 Jan 2017 20:24:05 -0000


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

Dikang Gu updated CASSANDRA-13080:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Ready to Commit)

committed as {{5f3b35981d28179606c52599d502de7a08b9b690}}

> 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)