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] [Commented] (CASSANDRA-4840) remnants of removed nodes remain after removal
Date Fri, 26 Oct 2012 12:47:13 GMT

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

Brandon Williams commented on CASSANDRA-4840:
---------------------------------------------

Yes, it can happen in 1.1.  Even on restart some kind of message sits in MS for the host that
I haven't tracked down yet.  Worth noting that at least the FD portion is a red herring, it's
dumping the gossiper's endpoint state map which of course contains hosts with dead state.
                
> 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
>
> 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