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

David Capwell updated CASSANDRA-20550:
--------------------------------------
    Status: Ready to Commit  (was: Review In Progress)

||Repo||Branch||Parent Branch||SHA||Status||
|https://github.com/dcapwell/cassandra.git|CASSANDRA-20550|trunk|8e9d2839d9205b7bbc7914804df6d7039155dcb0|Unstable

Failed Builds:
||Build||Result||Reason||
| jvm-dtest-simulator   | fail | Test 
org.apache.cassandra.simulator.test.HarrySimulatorTest::test-cassandra.testtag_IS_UNDEFINED
 had |
| jvm-upgrade-dtests    | fail | Test 
org.apache.cassandra.distributed.upgrade.ClusterMetadataUpgradeHarryTest::simpleUpgradeTest-_jd
 |
| jvm11-dtests-fuzz     | fail | Test 
junit.framework.TestSuite::org.apache.cassandra.fuzz.sai.MultiNodeSAITest-_jdk11
 had an error   |
| python-dtests         | fail | Test 
gossip_test.TestGossip::gossip_test.py::TestGossip::test_2dc_parallel_startup 
failed,Test gossi |
| python-upgrade-dtests | fail | Test 
upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_4_1_x_To_indev_trunk::upgrade_tests.py
 |


> AST fuzz tests can be flakey in multi node clusters due to ephemeral read 
> errors caused by a race condition issue with SAIUtils test class
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-20550
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20550
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Test/fuzz
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>             Fix For: 5.x
>
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> SAIUtil only checks the status for the indexes on node1, which knows that 
> node2/node3 have completed the indexing... but doesn't confirm that node2 
> knows about node3 or that node3 knows about node2... this causes a flaky race 
> condition where we start a query on node2, node2 then sees that node3 is 
> still building the index (it isn't, this is based off gossip), so node2 
> rejects the query!



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