You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (Jira)" <ji...@apache.org> on 2020/10/22 11:44:00 UTC
[jira] [Updated] (CASSANDRA-16094) Avoid marking shutting down
nodes as up after receiving gossip shutdown message
[ https://issues.apache.org/jira/browse/CASSANDRA-16094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson updated CASSANDRA-16094:
----------------------------------------
Summary: Avoid marking shutting down nodes as up after receiving gossip shutdown message (was: Flaky Test: TestIncRepair.test_repaired_tracking_with_mismatching_replicas)
> Avoid marking shutting down nodes as up after receiving gossip shutdown message
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-16094
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16094
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
> Reporter: Caleb Rackliffe
> Assignee: Marcus Eriksson
> Priority: Normal
> Labels: dtest, incremental_repair, repair
> Fix For: 3.0.x, 3.11.x, 4.0-beta
>
>
> We have two recent failures for this test on trunk:
> 1.) https://app.circleci.com/pipelines/github/maedhroz/cassandra/102/workflows/37ed8dab-9da4-4730-a883-20b7a99d88b4/jobs/518/tests (CASSANDRA-15909)
> 2.) https://app.circleci.com/pipelines/github/jolynch/cassandra/6/workflows/41e080e0-d7ff-4256-899e-b4010c6ef5ab/jobs/716/tests (CASSANDRA-15379)
> The test expects there to be mismatches and then read repair executed on a following SELECT, but either those mismatches aren’t there, read repair isn’t happening, or both.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org