cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10238) Consolidating racks violates the RF contract
Date Fri, 11 Sep 2015 15:41:46 GMT

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

Brandon Williams commented on CASSANDRA-10238:
----------------------------------------------

bq. Do we also need more dtests? 

Given that we gave snitches the ability to change racks/DCs since their inception but never
thought about actually providing the infrastructure to support doing so, having more tests
around it seems prudent at this point.

> 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: Stefania
>            Priority: Critical
>
> 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)

Mime
View raw message