cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10243) Warn or fail when changing cluster topology live
Date Tue, 10 Nov 2015 09:57:11 GMT

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

Stefania commented on CASSANDRA-10243:
--------------------------------------

So far I've done {{GossipingPropertyFileSnitch}} and {{PropertyFileSnith}} in 2.1. Here is
what the error looks like:

{code}
ERROR 09:51:55 Cannot update data center or rack from [DC1, RAC1] to [DC2, RAC2] for live
host /127.0.0.1, property file NOT RELOADED
{code}

cc [~jbellis] and [~tjake] regarding the two questions above and summarized here:

* Should we enhance the deprecated snitch {{YamlFileNetworkTopologySnitch}} which is available
in 2.1 only
* Should we  allow a node to join the cluster when the rack changes on startup 
 

> Warn or fail when changing cluster topology live
> ------------------------------------------------
>
>                 Key: CASSANDRA-10243
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10243
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Jonathan Ellis
>            Assignee: Stefania
>            Priority: Critical
>             Fix For: 2.1.x
>
>
> Moving a node from one rack to another in the snitch, while it is alive, is almost always
the wrong thing to do.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message