Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 9 Oct 2015 03:08:26 +0000 (UTC)
From: "Joel Knighton (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12860713.1441034882000.65402.1444360106854@Atlassian.JIRA>
In-Reply-To: <JIRA.12860713.1441034882000@Atlassian.JIRA>
References: <JIRA.12860713.1441034882000@Atlassian.JIRA>
 <JIRA.12860713.1441034882695@arcas>
Subject: [jira] [Commented] (CASSANDRA-10231) Null status entries on nodes
 that crash during decommission of a different node
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Joel Knighton commented on CASSANDRA-10231:
-------------------------------------------

I agree on having a consistent behavior between {{updateTokens}}, {{updatePreferredIP}}, and {{removeEndpoint}}.

I'm working on concretely documenting the current behavior with log entries as I want to fully ensure I understand the sequence of actions causing the problem. I'll update the ticket when I have this complete.

> Null status entries on nodes that crash during decommission of a different node
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10231
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10231
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Joel Knighton
>            Assignee: Stefania
>             Fix For: 3.0.0 rc2
>
>         Attachments: n1.log, n2.log, n3.log, n4.log, n5.log
>
>
> This issue is reproducible through a Jepsen test of materialized views that crashes and decommissions nodes throughout the test.
> In a 5 node cluster, if a node crashes at a certain point (unknown) during the decommission of a different node, it may start with a null entry for the decommissioned node like so:
> DN 10.0.0.5 ? 256 ? null rack1
> This entry does not get updated/cleared by gossip. This entry is removed upon a restart of the affected node.
> This issue is further detailed in ticket [10068|https://issues.apache.org/jira/browse/CASSANDRA-10068].


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)