You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks a lot for this amazing educational tool. It's really a joy to use this tool for quick prototyping and testing protocols when learning.
I would like to know, if there is a way to inject node crashes as part of test suite?
For instance, in the unique-ids workload, running the test with a single node that simply increments a global variable results in all tests passing. However, in practice, if the node restarts, the generated IDs are no longer unique.
There's nothing for node crashes right now. I'd like to do it, just haven't had time.
If you'd like to experiment, I'd suggest adding a jepsen.nemesis/Nemesis which talks to maelstrom.process to kill/restart nodes, and adding a schedule for kill/start operations to the generator. You'll have to work out something for per-node persistent storage, and how to turn on, off, and schedule the faults.
First of all, thanks a lot for this amazing educational tool. It's really a joy to use this tool for quick prototyping and testing protocols when learning.
I would like to know, if there is a way to inject node crashes as part of test suite?
For instance, in the unique-ids workload, running the test with a single node that simply increments a global variable results in all tests passing. However, in practice, if the node restarts, the generated IDs are no longer unique.
Sample code
How it was run
Thank you
The text was updated successfully, but these errors were encountered: