cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <>
Subject [jira] [Comment Edited] (CASSANDRA-9474) Validate dc information on startup
Date Mon, 30 Nov 2015 15:12:11 GMT


Philip Thompson edited comment on CASSANDRA-9474 at 11/30/15 3:11 PM:

I believe this is good to commit w/ regards to CI, as none of the replication tests appear
to fail, but the hundreds of failing upgrade tests are concerning. Are these related [~pauloricardomg]?

was (Author: philipthompson):
Yes, I believe this is good to commit w/ regards to CI

> Validate dc information on startup
> ----------------------------------
>                 Key: CASSANDRA-9474
>                 URL:
>             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 file. Should this really be possible?
In the documentation at
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
> 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

View raw message