# Replaced one dead node and new node came up same hostid in scylla 4.6
**URL:** https://forum.scylladb.com/t/replaced-one-dead-node-and-new-node-came-up-same-hostid-in-scylla-4-6/4325
**Category:** ScyllaDB
**Tags:** troubleshooting, administration, cluster-management
**Created:** [January 3, 2025, 6:29pm UTC](https://forum.scylladb.com/t/replaced-one-dead-node-and-new-node-came-up-same-hostid-in-scylla-4-6/4325 "2025-01-03T18:29:00Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Ranjeet\_Kumar](https://forum.scylladb.com/u/Ranjeet_Kumar)
#### Post date: [January 3, 2025, 6:29pm UTC](https://forum.scylladb.com/t/replaced-one-dead-node-and-new-node-came-up-same-hostid-in-scylla-4-6/4325/1 "2025-01-03T18:29:00Z")
Replaced one dead node and new node came up with same hostid in scylla 4.6.
We have replaced one dead node and the new node came up with same hostid.we are getting below Host ID collision in log.Could you please help on it.Please find below log
Jan 3 18:10:14 ip-10-233-65-246 scylla: [shard 0] gossip - 60000 ms elapsed, gossip quarantine over
Jan 3 18:10:15 ip-10-233-65-246 scylla: [shard 0] storage\_service - Host ID collision for between and ; ignored
Jan 3 18:10:15 ip-10-233-65-246 scylla: [shard 0] storage\_service - handle\_state\_normal: Nodes and have the same token -9212246330932197951. Ignoring
Jan 3 18:10:15 ip-10-233-65-246 scylla: [shard 0] storage\_service - handle\_state\_normal: Nodes and have the same token -2023138897313104219. Ignoring
Jan 3 18:10:15 ip-10-233-65-246 scylla: [shard 0] storage\_service - handle\_state\_normal: Nodes and have the same token 4660978197628450497. Ignoring
Jan 3 18:10:15 ip-10-233-65-246 scylla: [shard 0] storage\_service - handle\_state\_normal: Nodes and have the same token -9091405894166869642. Ignoring
Jan 3 18:10:15 ip-10-233-65-246 scylla: [shard 0] storage\_service - handle\_state\_normal: Nodes and have the same token 1716034972238154026. Ignoring
Jan 3 18:10:15 ip-10-233-65-246 scylla: [shard 0] storage\_service - handle\_state\_normal: Nodes and have the same token 202759629005760746. Ignoring
---
### Author:  [@Guy](https://forum.scylladb.com/u/Guy)
#### Post date: [January 5, 2025, 6:49am UTC](https://forum.scylladb.com/t/replaced-one-dead-node-and-new-node-came-up-same-hostid-in-scylla-4-6/4325/2 "2025-01-05T06:49:39Z")
Hi Ranjeet, 4.6 is old and no longer supported. Please upgrade to the latest version and let me know if the problem still occurs.
---
### Author:  [@Ranjeet\_Kumar](https://forum.scylladb.com/u/Ranjeet_Kumar)
#### Post date: [January 5, 2025, 1:05pm UTC](https://forum.scylladb.com/t/replaced-one-dead-node-and-new-node-came-up-same-hostid-in-scylla-4-6/4325/3 "2025-01-05T13:05:57Z")
Hi Guy, As the cluster is unstable so we can not proceed with upgrade.As one node was terminated and trying to replace that node but cluster topology change is not working.(replace node and removenode ) is not working. even try to remove the dead node but not able to remove that node and getting below error
Jan 3 20:03:22 ip-10-233-64-213 scylla: [shard 0] storage\_service - removenode[0694a7e0-361f-4d07-94a9-e97b962de6aa]: Added node= as leaving node, coordinator=
Jan 3 20:04:27 ip-10-233-64-213 scylla: [shard 0] storage\_service - removenode[0694a7e0-361f-4d07-94a9-e97b962de6aa]: Node is down for node\_ops\_cmd verb
Jan 3 20:04:27 ip-10-233-64-213 scylla: [shard 0] storage\_service - removenode[0694a7e0-361f-4d07-94a9-e97b962de6aa]: Node is down for node\_ops\_cmd verb
Jan 3 20:04:27 ip-10-233-64-213 scylla: [shard 0] storage\_service - removenode[0694a7e0-361f-4d07-94a9-e97b962de6aa]: Node is down for node\_ops\_cmd verb
Jan 3 20:08:16 ip-10-233-64-213 scylla: [shard 0] storage\_service - Operation removenode is in progress, wait for it to complete
Jan 3 20:08:17 ip-10-233-64-213 scylla: [shard 0] storage\_service - No tokens to force removal on, call ‘removenode’