cassandra-commits mailing list archives

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

    [ https://issues.apache.org/jira/browse/CASSANDRA-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780245#comment-13780245
] 

Christopher J. Bottaro commented on CASSANDRA-6053:
---------------------------------------------------

Is there a way to manually fix the system.peers table once it's in the messed up state?  Like
a nodetool command or simply using CQL to delete the bad rows?
                
> system.peers table not updated after decommissioning nodes in C* 2.0
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-6053
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6053
>             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: http://www.atlassian.com/software/jira

Mime
View raw message