[ 
https://issues.apache.org/jira/browse/HDDS-15561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18093724#comment-18093724
 ] 

Chung-En Lee commented on HDDS-15561:
-------------------------------------

Hi [~adoroszlai] ,

My current plan includes:
 # Deploying Ozone via Docker Compose and verifying its S3 behavior.

 # Starting up `{{{}MiniOzoneCluster`{}}} to verify its behavior.

After that, I'm considering adding some fault injection to see how Ozone 
behaves under chaotic conditions. For this, I’m thinking about using 
`{{{}MiniChaosOzoneCluster`{}}}, or I might explore other ways to inject faults 
later on.


Once I have a more complete plan, I’ll submit a design doc PR for everyone to 
review.

> Introduce a linearizability checker to validate Ozone
> -----------------------------------------------------
>
>                 Key: HDDS-15561
>                 URL: https://issues.apache.org/jira/browse/HDDS-15561
>             Project: Apache Ozone
>          Issue Type: Test
>            Reporter: Chung-En Lee
>            Assignee: Chung-En Lee
>            Priority: Major
>
> To catch subtle consistency regressions like {{HDDS-15052}} without the 
> massive engineering overhead of full DST (Deterministic Simulation Testing), 
> we propose introducing a post-facto *Linearizability Checker* (e.g., 
> Porcupine, Elle, or Java alternatives).
> By acting as a black-box oracle, the checker will analyze concurrent client 
> operation histories generated by our existing {{MiniOzoneChaosCluster or 
> docker cluster}} to verify strict correctness with zero core code 
> invasiveness.
> Importantly, this checker will also serve as a foundational building block 
> for future DST efforts, as any deterministic simulation framework will still 
> require such an oracle to validate its execution histories.



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