Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 26 Oct 2012 21:07:13 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1954519915.33569.1351285633069.JavaMail.jiratomcat@arcas>
In-Reply-To: <1436617048.3434.1350685812157.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (CASSANDRA-4840) remnants of removed nodes remain
 after removal
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams updated CASSANDRA-4840:
----------------------------------------

    Reviewer: vijay2win@yahoo.com
    
> 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