> I replaced it with a new node, IP 10.16.128.197 and again token 0 with a > "-Dcassandra.replace_token=0" at startup Good Good.
How long ago did you bring the new node on ? There is a fail safe to remove 128.210 after 3 days if it does not gossip to other nodes. I *thought* that remove_token would remove the old IP from the ring. Can you post the output from nodetool gossipinfo from the 128.197 node ? Thanks ----------------- Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 19/10/2012, at 2:44 AM, Thomas van Neerijnen <t...@bossastudios.com> wrote: > Hi all > > I'm running Cassandra 1.0.11 on Ubuntu 11.10. > > I've got a ghost node which keeps showing up on my ring. > > A node living on IP 10.16.128.210 and token 0 died and had to be replaced. > I replaced it with a new node, IP 10.16.128.197 and again token 0 with a > "-Dcassandra.replace_token=0" at startup. This all went well but now I'm > seeing the following weirdness constantly reported in the log files around > the ring: > > INFO [GossipTasks:1] 2012-10-18 13:39:22,441 Gossiper.java (line 632) > FatClient /10.16.128.210 has been silent for 30000ms, removing from gossip > INFO [GossipStage:1] 2012-10-18 13:40:25,933 Gossiper.java (line 838) Node > /10.16.128.210 is now part of the cluster > INFO [GossipStage:1] 2012-10-18 13:40:25,934 Gossiper.java (line 804) > InetAddress /10.16.128.210 is now UP > INFO [GossipStage:1] 2012-10-18 13:40:25,937 StorageService.java (line 1017) > Nodes /10.16.128.210 and /10.16.128.197 have the same token 0. Ignoring > /10.16.128.210 > INFO [GossipTasks:1] 2012-10-18 13:40:37,509 Gossiper.java (line 818) > InetAddress /10.16.128.210 is now dead. > INFO [GossipTasks:1] 2012-10-18 13:40:56,526 Gossiper.java (line 632) > FatClient /10.16.128.210 has been silent for 30000ms, removing from gossip
