[
https://issues.apache.org/jira/browse/CASSANDRA-10242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954688#comment-14954688
]
Sylvain Lebresne commented on CASSANDRA-10242:
----------------------------------------------
Happy to commit this but are we sure we want to take any risk on 2.1 for this?
I'm particularly nervous with that change to
{{conf/cassandra-rackdc.properties}}: are we 100% certain it won't break any
upgrader using {{GossipingPropertyFileSnitch}}?
Also, the branch remove a seemingly unrelated line in the changelog, I suppose
that's an oversight?
> Validate rack information on startup
> ------------------------------------
>
> Key: CASSANDRA-10242
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10242
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Assignee: Carl Yeksigian
> Fix For: 3.0.0 rc2, 2.2.3, 2.1.11
>
>
> Moving to a new rack means that different data should be stored on a node.
> We already persist rack information in a system table; we should fail startup
> if this doesn't match what the snitch thinks it should be. (Either the
> snitch is wrong, and needs to be fixed, or the machine has been moved and
> needs to be rebootstrapped.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
