[
https://issues.apache.org/jira/browse/CASSANDRA-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112382#comment-13112382
]
Jason Harvey commented on CASSANDRA-3243:
-----------------------------------------
Looking through the logs, the node which saw the decommissioned node didn't
print anything about discovering it via gossip. The very first log line I have
regarding the phantom node is when I forced a removetoken.
> Node which was decommissioned and shut-down reappears on a single node
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-3243
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3243
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.8.5
> Reporter: Jason Harvey
> Priority: Minor
>
> I decommissioned a node several days ago. It was no longer in the ring list
> on any node in the ring. However, it was in the dead gossip list.
> In an attempt to clean it out of the dead gossip list so I could truncate, I
> shut down the entire ring and bought it back up. Once the ring came back up,
> one node showed the decommissioned node as still in the ring in a state of
> 'Down'. No other node in the ring shows this info.
> I successfully ran removetoken on the node to get that phantom node out.
> However, it is back in the dead gossip list, preventing me from truncating.
> Where might the info on this decommissioned node be being stored? Is HH
> possibly trying to deliver to the removed node, thus putting it back in the
> ring on one node?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
