[
https://issues.apache.org/jira/browse/CASSANDRA-10238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744695#comment-14744695
]
Stefania commented on CASSANDRA-10238:
--------------------------------------
Thanks for the review. I was relying on Gossip to eventually propagate the
changes of other hosts. I now closed this window for
{{YamlFileNetworkTopologySnitch}} and {{PropertyFileSnitch}} by updating all
endpoints whose dc or rack have changed in the configuration file.
I've also prepared the 2.0, 2.2 and 3.0 patches, see attached. They are
identical except:
* {{GossipingPropertyFileSnitch}} does not seem capable of updating its
configuration in 2.0
* {{YamlFileNetworkTopologySnitch}} was deleted in 2.2.
[~brandon.williams] what was the snitch in use when the original problem in 2.0
was reported?
> 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)
