Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CDC681781F for ; Mon, 25 May 2015 14:54:17 +0000 (UTC) Received: (qmail 37963 invoked by uid 500); 25 May 2015 14:54:17 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 37920 invoked by uid 500); 25 May 2015 14:54:17 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 37908 invoked by uid 99); 25 May 2015 14:54:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 May 2015 14:54:17 +0000 Date: Mon, 25 May 2015 14:54:17 +0000 (UTC) From: "Marcus Olsson (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-9474) DC/Rack property changed on live system MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Marcus Olsson created CASSANDRA-9474: ---------------------------------------- Summary: DC/Rack property changed on live system Key: CASSANDRA-9474 URL: https://issues.apache.org/jira/browse/CASSANDRA-9474 Project: Cassandra Issue Type: Bug Components: Core Environment: Cassandra 2.1.5 Reporter: Marcus Olsson 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)