[
https://issues.apache.org/jira/browse/CASSANDRA-10238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802673#comment-14802673
]
Stefania commented on CASSANDRA-10238:
--------------------------------------
I think we have CASSANDRA-10243 for a discussion on switching racks. The idea
so far is not to allow it.
bq. but invalidation should also be done on gossiped changes.
Yes we should call {{invalidateCachedRings()}} when the gossipped properties
change.
bq. The updateTopology call in the snitches belongs within reloadConfiguration
at the existing cache invalidation site.
No because this is called in the snitch constructor as well, where we cannot
update topology since the snitch does not exist yet.
bq. While we are in this, we should fix the same issue in
StorageService.updateSnitch.
Yes this is a valid point too.
I'm not sure if we should re-open this ticket or implement as part of
CASSANDRA-10243.
> 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)
