micropelago/garage
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

jepsen: got a failure with set1

Browse Source
This commit is contained in:
Alex Auvolat 2023-10-24 17:45:22 +02:00
parent d7ab2c639e
commit 4fa2646a75
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
script/jepsen.garage/README.md
View File

@ -77,17 +77,16 @@ Results with timestamp patch (`--patch tsfix2`):
### Set, basic test (write some items, then read) ### 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: Results:
- For now, no failures with clock-scramble nemesis + partition nemesis -> TODO long test run - 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 - **Fails with the partition + layout reconfiguration nemesis** (`--scenario pr`).
EXample of a failed run: `garage set1/20231024T172214.488+0200` (1 failure in 4 runs).
TODO: make it fail!!!
### Set, continuous test (interspersed reads and writes) ### Set, continuous test (interspersed reads and writes)