[
https://issues.apache.org/jira/browse/CASSANDRA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557312#comment-13557312
]
Sylvain Lebresne commented on CASSANDRA-5167:
---------------------------------------------
+1 with the nit that in excise I think we can call the new removeEndpoint
instead of doing both call separately.
> 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
> Fix For: 1.2.1
>
> Attachments: 5167.txt, 5167-v2.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
