Changing the rack of a live node is discouraged, since the ring ranges the node is responsible for will change, meaning the node will not own part of the data for its new ranges and other nodes may not have some of its current data.
It will be a forbidden operation in the upcoming versions of Cassandra, since it has caused trouble before, see https://issues.apache.org/jira/browse/CASSANDRA-10242 for more background. The safest thing is to decommission the node and bootstrap the node again in a new rack, as Jack suggested. 2015-11-26 14:40 GMT-08:00 Jack Krupansky <jack.krupan...@gmail.com>: > What RF are you using? How many data centers? What rack configuration are > you currently using/ Are you in fact using a rack-aware network topology > partitioner? > > Specifically, what are you attempting to accomplish - why change the rack > at all? Not that changing the rack is necessarily bad, just to clarify your > objective. > > See: > > http://docs.datastax.com/en/cassandra/2.0/cassandra/architecture/architectureDataDistributeReplication_c.html > > You may just have to bootstrap the new node with the proper rack and then > run repair on the nodes which formerly held replicas of the old node. > > Or, you may have to run a full repair for all nodes of the cluster: > > http://docs.datastax.com/en/cassandra/2.0/cassandra/operations/opsMoveNodeRack.html > > > -- Jack Krupansky > > On Thu, Nov 26, 2015 at 4:02 AM, Badrjan <badr...@tuta.io> wrote: > >> So I have a 8 node cluster and I would like to change the rack of one >> node. How should I do that? >> >> B. >> > >
