[
https://issues.apache.org/jira/browse/CASSANDRA-16094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-16094:
----------------------------------------
Fix Version/s: (was: 4.0-beta)
(was: 3.11.x)
(was: 3.0.x)
4.0-beta3
3.11.9
3.0.23
Since Version: 2.0 beta 1
Source Control Link:
https://github.com/apache/cassandra/commit/12604456f9a8a38f742fd536af145d6ef0f61677
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
committed, thanks!
> 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.23, 3.11.9, 4.0-beta3
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
