cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher J. Bottaro (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6053) system.peers table not updated after decommissioning nodes in C* 2.0
Date Fri, 27 Sep 2013 21:18:05 GMT


Christopher J. Bottaro commented on CASSANDRA-6053:

I did a "truncate peers" and it hasn't repopulated (I waited about 10 mins).  Do I need to
restart one or more nodes to trigger repopulating of the table?
> system.peers table not updated after decommissioning nodes in C* 2.0
> --------------------------------------------------------------------
>                 Key: CASSANDRA-6053
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Datastax AMI running EC2 m1.xlarge instances
>            Reporter: Guyon Moree
>            Assignee: Brandon Williams
>         Attachments: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message