[jira] [Updated] (CASSANDRA-9474) Validate dc information on startup

["Paulo Motta (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paulo Motta updated CASSANDRA-9474:
-----------------------------------
    Fix Version/s: 3.0.x
                   2.2.x
                   3.2
                   3.1
          Summary: Validate dc information on startup  (was: DC/Rack property changed on live system)

> Validate dc information on startup
> ----------------------------------
>
>                 Key: CASSANDRA-9474
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9474
>             Project: Cassandra
>          Issue Type: Improvement
>         Environment: Cassandra 2.1.5
>            Reporter: Marcus Olsson
>            Assignee: Marcus Olsson
>             Fix For: 3.1, 3.2, 2.1.x, 2.2.x, 3.0.x
>
>         Attachments: CASSANDRA-9474-2.2.patch, CASSANDRA-9474-dtest.patch, CASSANDRA-9474-trunk.patch, cassandra-2.1-9474.patch, cassandra-2.1-dc_rack_healthcheck.patch
>
>
> When using GossipingPropertyFileSnitch it is possible to change the data center and rack of a live node by changing the cassandra-rackdc.properties file. Should this really be possible? In the documentation at http://docs.datastax.com/en/cassandra/2.1/cassandra/initialize/initializeMultipleDS.html it's stated that you should ??Choose the name carefully; renaming a data center is not possible??, but with this functionality it doesn't seem impossible(maybe a bit hard with changing replication etc.).
> This functionality was introduced by CASSANDRA-5897 so I'm guessing there is some use case for this?
> Personally I would want the DC/rack settings to be as restricted as the cluster name, otherwise if a node could just join another data center without removing it's local information couldn't it mess up the token ranges? And suddenly the old data center/rack would loose 1 replica of all the data that the node contains.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)