[
https://issues.apache.org/jira/browse/CASSANDRA-10242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14877145#comment-14877145
]
Brandon Williams commented on CASSANDRA-10242:
----------------------------------------------
Some kind of -D override would be nice for the rare situation where you do blow
away the data in a dc or something and want to change the racks, but don't want
to have to blow away your entire system table and regenerate tokens, etc.
> 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: 2.1.x
>
>
> 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)
