cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Coli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5780) nodetool status and ring report incorrect/stale information after decommission
Date Sat, 04 Jan 2014 00:04:50 GMT

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

Robert Coli commented on CASSANDRA-5780:
----------------------------------------

I have always been of the opinion that a post-decommission node should forget its locally
stored state; I was surprised when I noticed that it didn't. 

For example, you told the node to relinquish the token ownership, why does it continue to
assert in its local state that it owns it? You told it to leave a cluster, the cluster is
the thing that has schema, why does it retain schema?

Is there a reason that a node should not just wipe all of its local persistent state on successful
decommission? That seems the simplest solution to all problems of non-sensically retained
state post-decommission.

> nodetool status and ring report incorrect/stale information after decommission
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5780
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5780
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Peter Haggerty
>            Priority: Trivial
>              Labels: lhf, ponies
>
> Cassandra 1.2.6 ring of 12 instances, each with 256 tokens.
> Decommission 3 of the 12 nodes, one after another resulting a 9 instance ring.
> The 9 instances of cassandra that are in the ring all correctly report nodetool status
information for the ring and have the same data.
> After the first node is decommissioned:
> "nodetool status" on "decommissioned-1st" reports 11 nodes
> After the second node is decommissioned:
> "nodetool status" on "decommissioned-1st" reports 11 nodes
> "nodetool status" on "decommissioned-2nd" reports 10 nodes
> After the second node is decommissioned:
> "nodetool status" on "decommissioned-1st" reports 11 nodes
> "nodetool status" on "decommissioned-2nd" reports 10 nodes
> "nodetool status" on "decommissioned-3rd" reports 9 nodes
> The storage load information is similarly stale on the various decommissioned nodes.
The nodetool status and ring commands continue to return information as if they were part
of a cluster and they appear to return the last information that they saw.
> In contrast the nodetool info command fails with an exception, which isn't ideal but
at least indicates that there was a failure rather than returning stale information.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message