I thought the same that the decommission would complete the removal of a node. I have heard something said about a 72 hour window, I’m not sure if that pertains to this version.
Thanks Mark 801-705-7115 office From: Hannu Kröger [mailto:hkro...@gmail.com] Sent: Tuesday, May 16, 2017 10:09 AM To: suraj pasuparthy <suraj.pasupar...@gmail.com> Cc: Mark Furlong <mfurl...@ancestry.com>; user@cassandra.apache.org Subject: Re: Decommissioned node cluster shows as down That’s weird. I thought decommission would ultimately remove the node from the cluster because the token(s) should be removed from the ring and data should be streamed to new owners. “DN” is IMHO not a state where the node should end up in. Hannu On 16 May 2017, at 19:05, suraj pasuparthy <suraj.pasupar...@gmail.com<mailto:suraj.pasupar...@gmail.com>> wrote: Yes, you have to run a nodetool removenode to decomission completely.. this will also allow another node with the same ip different HashId to join the cluster.. Thanks -suraj On Tue, May 16, 2017 at 9:01 AM Mark Furlong <mfurl...@ancestry.com<mailto:mfurl...@ancestry.com>> wrote: I have a node I decommissioned on a large ring using 2.1.12. The node completed the decommission process and is no longer communicating with the rest of the cluster. However when I run a nodetool status on any node in the cluster it shows the node as ‘DN’. Why is this and should I just run a removenode now? Thanks, Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043 <image003.png>
