cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Failbus (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6053) system.peers table not updated after decommissioning nodes in C* 2.0
Date Tue, 03 Nov 2015 14:30:28 GMT


Kenneth Failbus commented on CASSANDRA-6053:

Even though, this was fixed it surfaced in 2.0.14 release that we have in production. We are
going to follow the work-around as mentioned above.

> system.peers table not updated after decommissioning nodes in C* 2.0
> --------------------------------------------------------------------
>                 Key: CASSANDRA-6053
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Datastax AMI running EC2 m1.xlarge instances
>            Reporter: Guyon Moree
>            Assignee: Tyler Hobbs
>             Fix For: 1.2.14, 2.0.5
>         Attachments: 6053-v1.patch, peers
> After decommissioning my cluster from 20 to 9 nodes using opscenter, I found all but
one of the nodes had incorrect system.peers tables.
> This became a problem (afaik) when using the python-driver, since this queries the peers
table to set up its connection pool. Resulting in very slow startup times, because of timeouts.
> The output of nodetool didn't seem to be affected. After removing the incorrect entries
from the peers tables, the connection issues seem to have disappeared for us. 
> Would like some feedback on if this was the right way to handle the issue or if I'm still
left with a broken cluster.
> Attached is the output of nodetool status, which shows the correct 9 nodes. Below that
the output of the system.peers tables on the individual nodes.

This message was sent by Atlassian JIRA

View raw message