Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B063218CB3 for ; Wed, 30 Sep 2015 05:21:06 +0000 (UTC) Received: (qmail 96439 invoked by uid 500); 30 Sep 2015 05:21:05 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 96260 invoked by uid 500); 30 Sep 2015 05:21:05 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 96079 invoked by uid 99); 30 Sep 2015 05:21:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Sep 2015 05:21:05 +0000 Date: Wed, 30 Sep 2015 05:21:05 +0000 (UTC) From: "Joel Knighton (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936383#comment-14936383 ] Joel Knighton edited comment on CASSANDRA-10231 at 9/30/15 5:20 AM: -------------------------------------------------------------------- I'll spend more time on this tomorrow (in CDT), but I have a branch that applies your 10231 patch on top of my 10413 patch (available at [10231-on-10413|https://github.com/jkni/cassandra/tree/10231-on-10413]). My 10413 branch is based on latest 3.0 With a build from the 10231-on-10413 branch, I'm no longer able to reproduce the issue. Again, I'll try repro-ing more tomorrow, but I haven't been able to produce any null status entries, which were fairly common before the patch. was (Author: jkni): I'll spent more time on this tomorrow (in CDT), but I have a branch that applies your 10231 patch on top of my 10413 patch (available at [10231-on-10413|https://github.com/jkni/cassandra/tree/10231-on-10413]). My 10413 branch is based on latest 3.0 With a build from the 10231-on-10413 branch, I'm no longer able to reproduce the issue. Again, I'll try repro-ing more tomorrow, but I haven't been able to produce any null status entries, which were fairly common before the patch. > 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)