[
https://issues.apache.org/jira/browse/CASSANDRA-10238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14803022#comment-14803022
]
Branimir Lambov commented on CASSANDRA-10238:
---------------------------------------------
It _is_ incomplete as affected nodes will use an obsolete cached view of the
ring for an indefinite amount of time. However, if changing racks is treated as
a forbidden operation this will not have any real effect so this should be
fixed as part of other tickets and not delay the release.
> 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
> Fix For: 2.0.17, 3.0.0 rc1, 2.1.10, 2.2.2
>
>
> 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)
