[
https://issues.apache.org/jira/browse/CASSANDRA-19757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872350#comment-17872350
]
Alex Petrov commented on CASSANDRA-19757:
-----------------------------------------
Probably the biggest argument here is that {{BurnTest}} never relied on
execution order. It was a construct added in {{AsyncOperation}} to make sure
replay is deterministic, but since now we are achieving log dereminism via
preserving outcomes rather than replaying commands, this feature became
redundant. And from what I can tell, the tests I have added ignore flag for
mainly tested this aspect of determinism. One way to preserve them is to port
execution order to the tests, but I think they will be testing themselves then.
We can try to create something more like {{BurnTest}}, maybe? But probably
simulator already covers this.
> Accord Journal / Determinism: Load Command states from the log
> ---------------------------------------------------------------
>
> Key: CASSANDRA-19757
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19757
> Project: Cassandra
> Issue Type: Improvement
> Components: Accord
> Reporter: Alex Petrov
> Assignee: Alex Petrov
> Priority: High
> Labels: pull-request-available
> Fix For: 5.1
>
> Attachments: ci_summary-1.html, ci_summary.html
>
>
> * Persist intermediate Command inthe journal
> * Simplify AccordJournal by removing Framing
> * Save command outcomes to the log
> * Reconstruct latest command state from the log entries
> * Replace `SerializerSupport#reconstruct` with log reconstruction
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
