Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 14 Jan 2016 02:18:39 +0000 (UTC)
From: "sankalp kohli (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12929662.1452652186000.105690.1452737919898@Atlassian.JIRA>
In-Reply-To: <JIRA.12929662.1452652186000@Atlassian.JIRA>
References: <JIRA.12929662.1452652186000@Atlassian.JIRA>
 <JIRA.12929662.1452652186170@arcas>
Subject: [jira] [Commented] (CASSANDRA-11005) Split consistent range
 movement flag
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

sankalp kohli commented on CASSANDRA-11005:
-------------------------------------------

Do you know the best way to check if it is running with vnodes? Just check if initial_token is null? 

> Split consistent range movement flag
> ------------------------------------
>
>                 Key: CASSANDRA-11005
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11005
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: sankalp kohli
>            Assignee: sankalp kohli
>            Priority: Trivial
>             Fix For: 2.1.12, 2.2.x, 3.x
>
>         Attachments: CASSANDRA_11005_2.1.diff, CASSANDRA_11005_2.2.diff
>
>
> CASSANDRA-7069 added a flag which does not allow multiple range movements in the ring. We want to turn this off as we want to move tokens far apart in the ring to speed up the moves. The problem is that this flag also turns off strict source check. We want to split this flag so that we can keep strict source but not stop parallel moves.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)