Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 1 Sep 2015 15:47:46 +0000 (UTC)
From: "Ryan McGuire (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12861048.1441122162000.223780.1441122466856@Atlassian.JIRA>
In-Reply-To: <JIRA.12861048.1441122162000@Atlassian.JIRA>
References: <JIRA.12861048.1441122162000@Atlassian.JIRA>
 <JIRA.12861048.1441122162528@arcas>
Subject: [jira] [Commented] (CASSANDRA-10238) Consolidating racks violates
 the RF contract
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ryan McGuire commented on CASSANDRA-10238:
------------------------------------------

Yep, @rhatch will write a dtest.

> Consolidating racks violates the RF contract
> --------------------------------------------
>
>                 Key: CASSANDRA-10238
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10238
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Russ Hatch
>
> I have only tested this on 2.0 so far, but I suspect it will affect multiple versions.
> Repro:
> * create a datacenter with rf>1
> * create more than one rack in this datacenter
> * consolidate these racks into 1
> * getendpoints will reveal the RF in practice is 1, even though other tools will report the original RF that was set
> Restarting Cassandra will resolve this.


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