[jira] [Updated] (CASSANDRA-18222) Fix flaky test org.apache.cassandra.distributed.test.accord.AccordIntegrationTest

["David Capwell (Jira)" <ji...@apache.org>]

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

David Capwell updated CASSANDRA-18222:
--------------------------------------
     Bug Category: Parent values: Correctness(12982)Level 1 values: Test Failure(12990)
       Complexity: Normal
    Discovered By: Unit Test
    Fix Version/s: 4.x
         Severity: Normal
           Status: Open  (was: Triage Needed)

> Fix flaky test org.apache.cassandra.distributed.test.accord.AccordIntegrationTest
> ---------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-18222
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18222
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Accord, CI
>            Reporter: David Capwell
>            Priority: Normal
>             Fix For: 4.x
>
>
> The accord integration tests are currently flaky due to Preempt happening (we convert that to a timeout).  We need to address this to make sure the tests are stable.
> One solution may be make SimpleProgressLog’s frequency run different for jvm-dtest (likely to depend on CASSANDRA-18221 ), this would be similar to what we already do as timeouts maybe larger in jvm-dtest due to the extra complexity running multiple processes in the same JVM.  Another solution may be to have the client coordinator “attach” to the new coordinator, this would avoid the user being impacted by this preempt when the coordinator is healthy.  



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

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org