You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jason Harvey (JIRA)" <ji...@apache.org> on 2011/09/24 00:31:26 UTC

[jira] [Issue Comment Edited] (CASSANDRA-3243) Node which was decommissioned and shut-down reappears on a single node

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

Jason Harvey edited comment on CASSANDRA-3243 at 9/23/11 10:30 PM:
-------------------------------------------------------------------

Clock on these boxes seems fine. We keep ntpd running at all times. I've also verified via logging that it has been consistent.

How do I go about getting that endpoint *out* of the LocationInfo?

      was (Author: alienth):
    Clock on these boxes seems fine. We keep ntpd running at all times. I've also verified via logging that it has been consistent.
  
> 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
>            Assignee: Brandon Williams
>            Priority: Minor
>         Attachments: locationinfo_0919.tgz, locationinfo_0922.tgz
>
>
> 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?
> I find it extremely curious that none of the other nodes in the ring showed the phantom node. Shouldn't gossip have propagated the node everywhere, even if it was down?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira