cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Williams <je...@wherethebitsroam.com>
Subject Re: Decommissioned node still in Gossip
Date Wed, 01 Jul 2015 07:23:14 GMT
Thanks for the tip Aiman, but this node is not in the seed list anywhere.

Jeff

On 30 June 2015 at 18:16, Aiman Parvaiz <aiman@flipagram.com> wrote:

> I was having exactly the same issue with the same version, check your seed
> list and make sure it contains only the live nodes, I know that seeds are
> only read when cassandra starts but updating the seed list to live nodes
> and then doing a roiling restart fixed this issue for me.
> I hope this helps you.
>
> Thanks
>
> Sent from my iPhone
>
> On Jun 30, 2015, at 4:42 AM, Jeff Williams <jeffw@wherethebitsroam.com>
> wrote:
>
> Hi,
>
> I have a cluster which had 4 datacenters running 2.0.12. Last week one of
> the datacenters was decommissioned using nodetool decommission on each of
> the servers in turn. This seemed to work fine until one of the nodes
> started appearing in the logs of all of the remaining servers with messages
> like:
>
>  INFO [GossipStage:3] 2015-06-30 11:22:39,189 Gossiper.java (line 924)
> InetAddress /172.29.8.8 is now DOWN
>  INFO [GossipStage:3] 2015-06-30 11:22:39,190 StorageService.java (line
> 1773) Removing tokens [...] for /172.29.8.8
>
> These come up in the log every minute or two. I believe it may have
> re-appeared after a repair, but I'm not sure.
>
> The problem is that this node does not exist in "nodetool status",
> "nodetool gossipinfo" or in the system.peers table. So how can tell the
> cluster that this node is decommissioned?
>
> Regards,
> Jeff
>
>

Mime
View raw message