You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefania (JIRA)" <ji...@apache.org> on 2015/11/18 10:59:11 UTC

[jira] [Comment Edited] (CASSANDRA-9474) DC/Rack property changed on live system

    [ https://issues.apache.org/jira/browse/CASSANDRA-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009972#comment-15009972 ] 

Stefania edited comment on CASSANDRA-9474 at 11/18/15 9:58 AM:
---------------------------------------------------------------

I think there is a fair bit of duplication with CASSANDRA-10243, which I am currently working on. Here we are blocking config reload if the rack or dc of a live node changes, for all snitches supporting config reload.


was (Author: stefania):
I think there is a fair bit of duplication with CASSANDRA-10243, which I am currently working on. Here were are blocking config reload if the rack or dc of a live node changes, for all snitches supporting config reload.

> 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-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)