cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Harvey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-3243) Node which was decommissioned and shut-down reappears on a single node
Date Thu, 22 Sep 2011 07:25:26 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Harvey updated CASSANDRA-3243:
------------------------------------

    Description: 
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?

  was:
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 every
node in the ring and brought them all back up. Once they all 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?


> 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

        

Mime
View raw message