You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Ivan Andika (Jira)" <ji...@apache.org> on 2026/10/07 01:15:00 UTC
[jira] [Commented] (RATIS-2542) Distributed System Testing in Ratis
[ https://issues.apache.org/jira/browse/RATIS-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124222#comment-18124222 ]
Ivan Andika commented on RATIS-2542:
------------------------------------
Thanks [~hooji], let me take a look when I have time and enough context. I also tried to experiment with Jepsen https://github.com/ivandika3/ratis/pull/1 , but did not see it through.
It would be helpful for me to see your methodology on using Jepsen for a bug hunting tool.
> Distributed System Testing in Ratis
> -----------------------------------
>
> Key: RATIS-2542
> URL: https://issues.apache.org/jira/browse/RATIS-2542
> Project: Ratis
> Issue Type: Test
> Components: test
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> This is a parent task for the effort to introduce distributed system testing to test the correctness of Ratis implementation as well provide proofs for Ratis-specific implementation (e.g. notifyInstallSnapshot correctness, repliedIndex linearizability proof, metadata entry, ratis group remove, etc). This would help to catch distributed system regressions and formalize implementation.
> Distributed system testing tools:
> * Jepsen, Ellen, Maelstorm
> * Fray
> * Hypothesis (Hegel)
> * Antithesis (paid)
> Distributed system proofs
> * TLA+
> ** Specula ([https://github.com/specula-org/Specula]) : AI generated TLA+ already used to find some Raft bugs
> * Lean4
> * P frameworks
> Articles
> * https://antithesis.com/blog/2026/finding-bugs-in-raft-implementations/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)