Re: strange gossip messages after node reboot with different ip

2012-05-08 Thread Piavlo
On 05/01/2012 04:16 AM, aaron morton wrote: Gossip information about a node can stay in the cluster for up to 3 days. How long has this been going on for ? This has been going for over a week already without any signs of slow down, all nodes that have changed ip popup as UP/DEAD endlessly. Any

Re: strange gossip messages after node reboot with different ip

2012-05-01 Thread Piavlo
Hi Aaron, Below is the reposted gossipinfo on a fresh 6 node cluster for which I stop/started all nodes one by one ~12hours ago, As you can see gossipinfo reports on 11 nodes, but what bothers me is why it reports STATUS:NORMAL for all of them and decides that non existing node is UP just o

strange gossip messages after node reboot with different ip

2012-04-30 Thread Piavlo
Hi, We have a cassandra cluster in ec2. If i stop a node and start it - as a result the node ip changes. The node is recognised as NEW node and is declared as replacing the previous node with same token.(But this is the same node of course) In this specific case the node ip before

Re: strange gossip messages after node reboot with different ip

2012-04-30 Thread aaron morton
Gossip information about a node can stay in the cluster for up to 3 days. How long has this been going on for ? I'm unsure if this is expected behaviour. But it sounds like Gossip is kicking out the phantom node correctly. Can you use nodetool gossipinfo on the nodes to capture some artefacts