cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4840) remnants of removed nodes remain after removal
Date Wed, 31 Oct 2012 08:47:12 GMT

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

Vijay commented on CASSANDRA-4840:
----------------------------------

Membership lock so no one else add's the node back into the map during the remove sequence,
it would be rare... +1 other than that.
                
> remnants of removed nodes remain after removal
> ----------------------------------------------
>
>                 Key: CASSANDRA-4840
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4840
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.10
>            Reporter: Jeremy Hanna
>            Assignee: Brandon Williams
>            Priority: Minor
>         Attachments: 4840.txt
>
>
> After nodes are removed from the ring and no longer appear in any of the nodes' nodetool
ring output, some of the dead nodes show up in the o.a.c.net.FailureDetector SimpleStates
metadata.  Also, some of the JMX stats are updating for the removed nodes (ie RecentTimeoutsPerHost
and ResponsePendingTasks).

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