cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4840) remnants of removed nodes remain after removal
Date Fri, 19 Oct 2012 22:38:12 GMT


Brandon Williams commented on CASSANDRA-4840:

I believe this may be evidence of the issue I've heard reported where nodes are still trying
to connect to dead IPs that were removed.  I suspect a message might be getting stuck in OTC
and causing this.

As far as the FD goes, we definitely remove it there in Gossiper.removeEndpoint, so something
must be adding it back.
> remnants of removed nodes remain after removal
> ----------------------------------------------
>                 Key: CASSANDRA-4840
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.10
>            Reporter: Jeremy Hanna
>            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 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:

View raw message