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

Brandon Williams commented on CASSANDRA-3243:
---------------------------------------------

bq. Is there a way I can get a list of endpoints to see how this node showed 
back up?

It must be a saved endpoint, if you can attached the latest LocationInfo 
sstable from that machine (and tell me the IP and/or token) I can take a look.

bq. Also, any thoughts on why this node only re-appeared on a single node?

I'm not sure, let's see if it was still persisted first.

> 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
>
> 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

        

Reply via email to