4 ms·

Looks like they were planning to Jepsen test later this year [0]. But it looks like they're preparing to run it themselves [1]? [0]: https://www.arangodb.com/2

by iamed2 10y ago

Looks like they were planning to Jepsen test later this year [0]. But it looks like they're preparing to run it themselves [1]? [0]: https://www.arangodb.com/2016/05/getting-closer-arangodb-3-0-alpha-release/ https://www.arangodb.com/2016/05/getting-closer-arangodb-3-0... [1]: https://github.com/arangodb/jepsen/commit/2b79809df73ca6c755ebe41a92f2b436860532b0 https://github.com/arangodb/jepsen/commit/2b79809df73ca6c755...

don71 10y ago
I'm an ArangoDB team member. We are starting with our own Jepsen tests. But we will ask Aphyr as soon as possible to do an official test. In the meantime can the community check our implementation.
- segmondy 10y ago
  It most certainly makes sense to jepsen Arango before asking the public to do so. But I won't take your tests without a grain of salt till Aphyr does so. ;) Best of luck
  - don71 10y ago
    As far as I know is Aphyer booked for months. We will do our best.
deleted 10y ago
[deleted]
Simran-B 10y ago
Jepsen tests are basically a closure framework to conduct such tests. We took some of the existing test cases and rewrote them for ArangoDB. So these are not "official Jepsen tests" but tests we did ourselves to track down issues. If you want to inspect and retest yourself, that will be possible. There's no reason to keep the tests closed source. Of course it would be great to get ArangoDB Aphyr-approved eventually.