cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anthony Grasso <>
Subject Re: Topology settings before/after decommission node
Date Thu, 11 Apr 2019 03:16:24 GMT
Hi Robert,

Your action plan looks good.

You can think of the ** file as a map for the
cluster. The map between the nodes must be consistent because each node
uses it to determine where it is meant to be located logically.

It is good hygiene to maintain the ** so it
contains only the IPs (broadcast addresses) currently used in the cluster.
Technically, you cloud leave the entry for the decommissioned node in
there. The problem is later on if that IP address is used by a node it will
be placed back in DC1 and this could be the wrong logical placement for it.
So I would advise removing the address if the node is inactive.

For step 3, there is no need to restart all the nodes. However if you do
want them to reload the configuration you will need to perform a rolling
restart on the cluster (i.e. restart one node at a time).


On Thu, 11 Apr 2019 at 03:38, rastrent <>

> Hi there,
> I am running a cassandra cluster (v3.0.9) with 2 DCs (4/3 nodes
> respectively) using endpoint_snitch: PropertyFileSnitch and I would like to
> decommission one node in DC1 but I wonder about what kind of actions I need
> to take related with the the topology settings.
> My has the those simple settings below:
> x.x.x.x=DC1:RAC1
> x.x.x.x=DC1:RAC1
> x.x.x.x=DC1:RAC1
> x.x.x.x=DC1:RAC1
> x.x.x.x=DC2:RAC1
> x.x.x.x=DC2:RAC1
> x.x.x.x=DC2:RAC1
> default=DC1:r1
> My action plan is to:
> 1)Decomission a node in DC1
> 2) After node leaves cluster,  edit in every
> node in the cluster
> 3) Question: No I need to restart all nodes in cluster? (one each time of
> course)
> Bonus question: Do I need to change the
> before move/remove nodes?
> Cheers,
> Robert,
> Sent with ProtonMail <> Secure Email.

View raw message