Re: replaced node keeps returning in gossip

2012-10-19 Thread Thomas van Neerijnen
Hi When I sent the mail I'd had the new node on for about an hour, the old node died about an hour before that. The weirdness in the log files stopped yesterday afternoon, about 4 or 5 hours after I replaced the node so it seems to have resolved itself. Seeing as there's no error to look at in the

Re: replaced node keeps returning in gossip

2012-10-18 Thread aaron morton
> 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

replaced node keeps returning in gossip

2012-10-18 Thread Thomas van Neerijnen
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 start