From 4fa2646a75ed9b4823bf36ae6218a18cca11c471 Mon Sep 17 00:00:00 2001 From: Alex Auvolat Date: Tue, 24 Oct 2023 17:45:22 +0200 Subject: [PATCH] jepsen: got a failure with set1 --- script/jepsen.garage/README.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/script/jepsen.garage/README.md b/script/jepsen.garage/README.md index e1dc6953..5d407b6a 100644 --- a/script/jepsen.garage/README.md +++ b/script/jepsen.garage/README.md @@ -77,17 +77,16 @@ Results with timestamp patch (`--patch tsfix2`): ### Set, basic test (write some items, then read) -Command: `lein run test --nodes-file nodes.vagrant --time-limit 60 --rate 100 --concurrency 100 --workload set1 --ops-per-key 100 --patch tsfix2` +Command: `lein run test --nodes-file nodes.vagrant --time-limit 60 --rate 200 --concurrency 200 --workload set1 --ops-per-key 100 --patch tsfix2` Results: - For now, no failures with clock-scramble nemesis + partition nemesis -> TODO long test run -- Does not seem to fail with only the layout reconfiguation nemesis (>20 runs), although theoretically it could +- Does not seem to fail with only the layout reconfiguation nemesis (<10 runs), although theoretically it could -- Does not seem to fail with the layout reconfiguation + partition nemesis (<10 runs), although theoretically it could - -TODO: make it fail!!! +- **Fails with the partition + layout reconfiguration nemesis** (`--scenario pr`). + EXample of a failed run: `garage set1/20231024T172214.488+0200` (1 failure in 4 runs). ### Set, continuous test (interspersed reads and writes)