[
https://issues.apache.org/jira/browse/CASSANDRA-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727388#comment-14727388
]
T Jake Luciani edited comment on CASSANDRA-10243 at 9/2/15 2:11 PM:
--------------------------------------------------------------------
bq. Are we confident that this is always the wrong thing?
Yes. We should track the rack name on startup and use while the node is up.
I'm not even sure if we should allow a node to join the cluster when the rack
changes on startup without an explicit operator intervention.
We should apply the same logic to DC movement.
was (Author: tjake):
bq. Are we confident that this is always the wrong thing?
Yes. We should track the rack name on startup and use while the node is up.
I'm not even sure if we should allow a node to join the cluster on startup
without an explicit operator intervention.
We should apply the same logic to DC movement.
> 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
> 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)
