[
https://issues.apache.org/jira/browse/CASSANDRA-10231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939224#comment-14939224
]
Stefania commented on CASSANDRA-10231:
--------------------------------------
I've removed the additional GOSSIP entry log message from the proper branch but
I've left the old branch with such entry in the
[10231-3.0-debug|https://github.com/stef1927/cassandra/commits/10231-3.0-debug]
branch.
I've tried reproducing the issue for 2.1 or 2.2 but couldn't, it seems
CASSANDRA-10298 is a slightly different issue after all (GOSSIP major update
with status LEFT but missing tokens and host id). Are you able to confirm with
Jepsen if 2.1 and 2.2 are affected or not?
I should also add the CI links for 3.0:
http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-10231-3.0-testall/
http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-10231-3.0-dtest/
> 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)
