cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Knighton (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-10231) Null status entries on nodes that crash during decommission of a different node
Date Mon, 31 Aug 2015 15:28:45 GMT
Joel Knighton created CASSANDRA-10231:
-----------------------------------------

             Summary: 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


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)

Mime
View raw message