[
https://issues.apache.org/jira/browse/CASSANDRA-10238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744428#comment-14744428
]
Blake Eggleston commented on CASSANDRA-10238:
---------------------------------------------
I think there's still a window of time where the RF contract violation is
possible. In {{YamlFileNetworkTopologySnitch}} and {{PropertyFileSnitch}},
{{StorageService.instance.updateTopology}} is only called for the local node,
although any of the nodes could have been updated. Assuming topology file
changes are deployed to all nodes simultaneously, this would mean that the
snitch and TokenMetadata will be out of sync until the node which has moved
picks up the changes in it's topology file and it's new application state
propagates to the out of sync node. Calling
{{StorageService.instance.updateTopology}} on any endpoint that changed should
fix that
> 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)
