After decommissioning the node remains in gossip for a period of 3 days (if I recall correctly) and it will show up on describecluster during that period, so this is expected behavior. This allows other nodes that eventually were down when the node decommissioned to learn that this node left the cluster.
What assassinate does is remove the node from gossip, so that's why it no longer shows up on describecluster, but this shouldn't be necessary. You should check that the node successfully decommissioned if it doesn't show up on "nodetool status". Em qui., 17 de set. de 2020 às 14:26, Krish Donald <gotomyp...@gmail.com> escreveu: > We are on 3.11.5 opensource cassandra > > On Thu, Sep 17, 2020 at 10:25 AM Krish Donald <gotomyp...@gmail.com> > wrote: > >> Hi, >> >> We decommissioned a node from the cluster. >> On decommissioned node it said in system.log that node has been >> decommissioned . >> But after couple of minutes only , on rest of the nodes the node is >> showing UNREACHABLE when we issue nodetool describecluster . >> >> nodetool status is not showing the node however nodetool describecluster >> is showing UNREACHABLE. >> >> I tried nodetool assassinate and now node is not showing in nodetool >> describecluster , however that seems to be the last option. >> >> Ideally it should leave the cluster immediately after decommission. >> Once decommissioned is completed as per log then is there any issue in >> issuing nodetool assasinate ? >> >> Thanks >> >>
