You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Philip Thompson (JIRA)" <ji...@apache.org> on 2015/03/29 19:34:52 UTC
[jira] [Updated] (CASSANDRA-8481) ghost node in gossip
[ https://issues.apache.org/jira/browse/CASSANDRA-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Thompson updated CASSANDRA-8481:
---------------------------------------
Reproduced In: 2.0.11
Fix Version/s: 2.0.14
> ghost node in gossip
> --------------------
>
> Key: CASSANDRA-8481
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8481
> Project: Cassandra
> Issue Type: Bug
> Reporter: Alexey Larkov
> Priority: Minor
> Fix For: 2.0.14
>
>
> After inaccurate removing nodes from cluster
> nodetool gossipinfo and jmx org.apache.cassandra.net.FailureDetector.AllEndpointsStates shows the node status is LEFT.
> Name Value Type Display Name Update Interval Description
> /192.168.58.75
> generation:3
> heartbeat:0
> REMOVAL_COORDINATOR:REMOVER,f9a28f8c-3244-42d1-986e-592aafe1406c
> STATUS:LEFT,-3361705224534889554,1418888446785
> jmx org.apache.cassandra.net.FailureDetector.DownEndpointCount is 1
> node 58.75 is absent in nodetool status and system.peers table.
> Before node got LEFT status it was in REMOVING state.
> I've done unsafeassassinateendpoint and it's status became LEFT, but DownEndpointCount is still 1.
> And org.apache.cassandra.net.FailureDetector.SimpleStates is still DOWN.
> How to remove this node from gossip?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)