[
https://issues.apache.org/jira/browse/CASSANDRA-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008522#comment-15008522
]
Marcus Olsson commented on CASSANDRA-9474:
------------------------------------------
I've started the implementation towards 2.2 and done a dtest for it. I have
just one question regarding the cassandra.ignore_dc flag, in the 2.2 branch I
can't seem to find the cassandra.ignore_rack flag
[here|https://github.com/apache/cassandra/commit/7cab3272455bdd16b639c510416ae339a8613414],
should I be consistent and not add it?
> DC/Rack property changed on live system
> ---------------------------------------
>
> 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: 2.1.x
>
> Attachments: 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)
