[
https://issues.apache.org/jira/browse/CASSANDRA-20550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-20550:
--------------------------------------
Fix Version/s: NA
(was: 5.x)
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/6b2cdba56b85b948a8716a02b2cd3015e8d1ff9a
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> 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: NA
>
> Attachments:
> ci_summary-trunk-8e9d2839d9205b7bbc7914804df6d7039155dcb0.html,
> result_details-trunk-8e9d2839d9205b7bbc7914804df6d7039155dcb0.tar.gz
>
> Time Spent: 2.5h
> 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]
