[
https://issues.apache.org/jira/browse/CASSANDRA-21189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18061131#comment-18061131
]
Sam Tunnicliffe commented on CASSANDRA-21189:
---------------------------------------------
I don't recall why those values specifically, but I bet it was just a fairly
arbitrary choice intended to speed up the test runtime. I'm sure it works fine
99.999% of the time locally but is flaky in environments with more constrained
resources, like CI. I think it would be reasonable to just bump that timeout a
bit and see if it improves the failure rate.
> Fix flaky DTest: InProgressSequenceCoordinationTest
> ---------------------------------------------------
>
> Key: CASSANDRA-21189
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21189
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
> Reporter: Sam Lightfoot
> Assignee: Sam Lightfoot
> Priority: Normal
> Fix For: 5.1
>
>
> There's a race condition between cluster closing and startup between test
> scenarios due to lack of thread lifecycle handling. The spawned thread should
> be joined before the test finishes to prevent the 'in-use port' errors.
> Affects
> * bootstrapProgressTest
> * decommissionProgressTest
> * replacementProgressTest
> Adopt the same pattern as GossipTest with try-finally thread joining.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
