Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <8543382.104521286919875537.JavaMail.jira@thor>
Date: Tue, 12 Oct 2010 17:44:35 -0400 (EDT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Assigned: (CASSANDRA-1609) Cluster restart re-adds removed
 tokens
In-Reply-To: <472222.98341286902293954.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis reassigned CASSANDRA-1609:
-----------------------------------------

    Assignee: Jonathan Ellis  (was: Nick Bailey)

> Cluster restart re-adds removed tokens
> --------------------------------------
>
>                 Key: CASSANDRA-1609
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1609
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7 beta 2
>            Reporter: Nick Bailey
>            Assignee: Jonathan Ellis
>             Fix For: 0.7.0
>
>
> After a cluster restart one of our nodes began reporting tokens that had been removed a good while ago (week or more) in it's nodetool ring output.  This probably has something to do with our change to persist the ring in CASSANDRA-1518 and removetoken changes in CASSANDRA-1216. The node didn't actually gossip the removed tokens so they showed up in TMD but not gossip.
> Additionally all nodes began reporting a node that had been removed maybe an hour ago.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.