[ 
https://issues.apache.org/jira/browse/CASSANDRA-21189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sam Lightfoot updated CASSANDRA-21189:
--------------------------------------
    Description: 
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

  was:
Tests often failing due to no seed no being up whilst non-seeds trying to join 
the ring. Likely fix to start the seed node to ensure CMS initialization is 
complete then allow other nodes in CCM to start in parallel.

Affects 5.1+ due to <=5.0 using [sequential 
startup|https://github.com/apache/cassandra-dtest/blob/trunk/bootstrap_test.py#L254C30-L254C32].

On further analysis it appears two separate clusters form due to the seed node 
not accepting messages during CMS initialization. Attached logs show the 
independent clusters resulting from 
_bootstrap_test.py::TestBootstrap::test_read_from_bootstrapped_node._


> 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/python
>            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



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to