cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5167) Node isn't removed from system.peers after 'nodetool removenode'
Date Thu, 17 Jan 2013 19:22:14 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brandon Williams updated CASSANDRA-5167:
----------------------------------------

    Attachment: 5167.txt

I'm not sure why we ever made a 'removeTokens' method instead of 'removeEndpoint' since we're
never going to want to remove some subset of a node's tokens.  Patch to delete endpoints.
                
> Node isn't removed from system.peers after 'nodetool removenode'
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-5167
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5167
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>         Environment: Ubuntu 12.10, Java 1.7.0_09 (OpenJDK)
>            Reporter: Nicolai Gylling
>            Assignee: Brandon Williams
>            Priority: Minor
>         Attachments: 5167.txt
>
>
> In a 3 node live cluster - After a replacement of a dead node, the old node remains in
the system.peers table, even after running 'nodetool removenode <ID>'.

--
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