[
https://issues.apache.org/jira/browse/CASSANDRA-21189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Lightfoot updated CASSANDRA-21189:
--------------------------------------
Test and Documentation Plan:
PR: [https://github.com/apache/cassandra/pull/4639]
CI:
[https://pre-ci.cassandra.apache.org/job/cassandra/440/]
[https://pre-ci.cassandra.apache.org/job/cassandra/441/]
[https://pre-ci.cassandra.apache.org/job/cassandra/442]
[https://pre-ci.cassandra.apache.org/job/cassandra/443]
was:
[https://github.com/apache/cassandra/pull/4639]
[https://pre-ci.cassandra.apache.org/job/cassandra/440/]
[https://pre-ci.cassandra.apache.org/job/cassandra/441/]
> 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.
> Per additional research, a constrained request_timeout causing a Paxos commit
> SERVER_ERROR was the initial trigger of the errors. The timeout is 1s in the
> tests, which can be troublesome when CI is slow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
