Re: Changing Racks of Nodes

[Ben Bromhead]

If the rack as defined in Cassandra stays the same (e.g.
cassandra-rackdc.properties), things will keep working as expected...
except when the actual rack (or fault domain) goes down and you are likely
to lose more nodes than expected.

If you change the rack as defined in Cassandra, the node will start
handling queries it does not have data for.

The best way to change the move racks is to decommission the node, then
bootstrap it with the new rack settings.

On Wed, 20 Apr 2016 at 15:49 Anubhav Kale 
wrote:

> Hello,
>
>
>
> If a running node moves around and changes its rack in the process, when
> its back in the cluster (through ignore-rack property), is it a correct
> statement that queries will not see some data residing on this node until a
> repair is run ?
>
>
>
> Or, is it more like the node may get requests for the data it does not own
> (meaning data will never “disappear”) ?
>
>
>
> I’d appreciate some details on this topic from experts !
>
>
>
> Thanks !
>
-- 
Ben Bromhead
CTO | Instaclustr 
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer

Changing Racks of Nodes

[Anubhav Kale]

Hello,

If a running node moves around and changes its rack in the process, when its 
back in the cluster (through ignore-rack property), is it a correct statement 
that queries will not see some data residing on this node until a repair is run 
?

Or, is it more like the node may get requests for the data it does not own 
(meaning data will never "disappear") ?

I'd appreciate some details on this topic from experts !

Thanks !