the generations are: - Wed, 23 Aug 2017 09:30:18 GMT - Fri, 25 Aug 2017 04:52:59 GMT I don't remember what we did at that time but it looks like we botched something while joining a node or something. After reading https://thelastpickle.com/blog/2018/09/18/assassinate.html I'm thinking of doing the following: * nodetool removenode 10.15.53.27 * if it doesn't work for some reason: nodetool assassinate 10.15.53.27 Since those nodes have been long dead and don't appear in system.peer I don't anticipate any problems but I'd like some confirmation that this can't break my cluster. Thanks ! --90dd1de351334223a928b76a993f77ce Content-Type: text/html Content-Transfer-Encoding: quoted-printable

Hi,

while replacing a node in a cluster I saw this lo= g:

2019-08-27 16:35:31,4= 39 Gossiper.java:995 - InetAddress /10.15.53.27 is now DOWN

it caught my attention because that ip address doesn't = exist anymore in the cluster and it hasn't for a long time.

After some reading I ran `nodetool gossipinfo` and I sa= w these entries which are nodes that don't exist anymore:

/10.15.53.27

= ; generation:1503480618

&nbs= p; heartbeat:26970

&nb= sp; STATUS:2:hibernate,true

= LOAD:26810:6.17363354147E11

= ; SCHEMA:101:d21b1e47-f226-3417-8de7-5802518ae824

&n= bsp; DC:10:DC1

&= nbsp; RACK:12:RAC1

RELEASE_= VERSION:6:2.1.18

INTERNAL_I= P:8:10.15.53.27

RPC_ADDRESS= :5:10.15.53.27

SEVERITY:269= 72:0.0

NET_VERSION:3:8
<= /div>

HOST_ID:4:2488fccc-108a-4a9d-ad= 43-5e8b8b6ee17b

TOKENS:1:&l= t;hidden>

/10.5.1.16

&= nbsp; generation:1503636779

= heartbeat:324

&= nbsp; STATUS:2:hibernate,true

&nbs= p; LOAD:204:2.601990697532E12

&nbs= p; SCHEMA:14:d21b1e47-f226-3417-8de7-5802518ae824

&n= bsp; DC:10:DC1

&= nbsp; RACK:12:RAC1

RE= LEASE_VERSION:6:2.1.18

INTE= RNAL_IP:8:10.5.1.16

RPC_ADD= RESS:5:10.5.1.16

SEVERITY:3= 26:0.0

NET_VERSION:3:8
<= /div>

HOST_ID:4:2488fccc-108a-4a9d-ad= 43-5e8b8b6ee17b

TOKENS:1:&l= t;hidden>

the generations are:

- Wed, 23 Aug 2017 09:30:18 GMT

- Fri,= 25 Aug 2017 04:52:59 GMT

I don't remember = what we did at that time but it looks like we botched something while jo= ining a node or something.

After reading htt= ps://thelastpickle.com/blog/2018/09/18/assassinate.html I'm thinking= of doing the following:

* nodetool removen= ode 10.15.53.27

* if it doesn't work for some reason: node= tool assassinate 10.15.53.27

Since those no= des have been long dead and don't appear in system.peer I don't anticipa= te any problems but I'd like some confirmation that this can't break my = cluster.

Thanks !

--90dd1de351334223a928b76a993f77ce--