[ https://issues.apache.org/jira/browse/CASSANDRA-10242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945762#comment-14945762 ]
Paulo Motta commented on CASSANDRA-10242: ----------------------------------------- Patch LGTM overall, could you just add a simple dtest changing the rack of a single node and check the node will fail to initialize? {{replication_test.py}} have some example of changing snitch/rack information. Also, is there any reason you changed the default rack and dc assignments of {{conf/cassandra-rackdc.properties}} ? > 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)