Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 12 Nov 2015 18:22:11 +0000 (UTC)
From: "Paulo Motta (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12832527.1432565611000.52611.1447352531132@Atlassian.JIRA>
In-Reply-To: <JIRA.12832527.1432565611000@Atlassian.JIRA>
References: <JIRA.12832527.1432565611000@Atlassian.JIRA>
 <JIRA.12832527.1432565611297@arcas>
Subject: [jira] [Updated] (CASSANDRA-9474) DC/Rack property changed on live
 system
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Paulo Motta updated CASSANDRA-9474:
-----------------------------------
    Assignee: Marcus Olsson
    Reviewer: Paulo Motta

> DC/Rack property changed on live system
> ---------------------------------------
>
>                 Key: CASSANDRA-9474
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9474
>             Project: Cassandra
>          Issue Type: Bug
>         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)