[
https://issues.apache.org/jira/browse/CASSANDRA-15792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162064#comment-17162064
]
Gianluca Righetto commented on CASSANDRA-15792:
-----------------------------------------------
Thanks for the first pass, [~Bereng]. Yes, this has been waiting for a
committer to do the final push, I'll check if there's anyone available.
I just realized I never added a comment detailing the final solution I landed
on, so here it goes: the original implementation didn't expect a {{speculative
write}} to be performed to node2, but depending on timing and load of node3,
that might actually happen. So, as long as we can guarantee the speculative
write to node2 happened after the initial write attempt to node3, we're good.
In order to achieve that, I implemented a byteman function that records the
{{System.currentTimeMillis}} of each Message Verb, and with that I can
reconstruct the order of the events in the test.
> test_speculative_data_request - read_repair_test.TestSpeculativeReadRepair
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-15792
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15792
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
> Reporter: Ekaterina Dimitrova
> Assignee: Gianluca Righetto
> Priority: Normal
> Fix For: 4.0-beta
>
>
> Failing on the latest trunk here:
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/127/workflows/dfba669d-4a5c-4553-b6a2-85647d0d8d2b/jobs/668/tests
> Failing once in 30 times as per Jenkins:
> https://jenkins-cm4.apache.org/job/Cassandra-trunk-dtest/69/testReport/dtest.read_repair_test/TestSpeculativeReadRepair/test_speculative_data_request/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
