Re: Decommissioning a new node when the state is JOINING

2019-04-30 Thread Akshay Bhardwaj
Thank you for prompt replies. The solutions worked! Akshay Bhardwaj +91-97111-33849 On Tue, Apr 30, 2019 at 5:56 PM ZAIDI, ASAD A wrote: > Just stop the server/kill C* process as node never fully joined the > cluster yet – that should be enough. You can safely remove the data i.e. >

RE: Decommissioning a new node when the state is JOINING

2019-04-30 Thread ZAIDI, ASAD A
Just stop the server/kill C* process as node never fully joined the cluster yet – that should be enough. You can safely remove the data i.e. streamed-in on new node so you can use the node for other new cluster. From: Akshay Bhardwaj [mailto:akshay.bhardwaj1...@gmail.com] Sent: Tuesday, April

Re: Decommissioning a new node when the state is JOINING

2019-04-30 Thread shalom sagges
I would just stop the service of the joining node and then delete the data, commit logs and saved caches. After stopping the node while joining, the cluster will remove it from the list (i.e. nodetool status) without the need to decommission. On Tue, Apr 30, 2019 at 2:44 PM Akshay Bhardwaj <

Decommissioning a new node when the state is JOINING

2019-04-30 Thread Akshay Bhardwaj
Hi Experts, I have a cassandra cluster running with 5 nodes. For some reason, I was creating a new cassandra cluster, but one of the nodes intended for new cluster had the same cassandra.yml file as the existing cluster. This resulted in the new node joining the existing cluster, making total no.