Re: Decommissioned node cluster shows as down

If the nodetool status shows DN, then you will need to tell the cluster to remove the memory of that node by running removenode. If that doesn't work, you may run assassinate - the ultimate command to shutdown the node. Thanks, Gedeon On Tue, May 16, 2017 at 12:01 PM, Mark Furlong

Re: RE: Decommissioned node cluster shows as down

On 2017-05-16 09:28 (-0700), Mark Furlong wrote: > 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. > We keep a record of it in

Re: Decommissioned node cluster shows as down

On 2017-05-16 09:08 (-0700), Hannu Kröger wrote: > 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

RE: Decommissioned node cluster shows as down

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) shoul

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

Re: Decommissioned node cluster shows as down

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 wrote: > > > > > > > > > > > > > > > > > I have a