Actually, we have a doc about how to test zookeeper with jepsen(https://github.com/apache/zookeeper/blob/master/zookeeper-docs/src/main/resources/markdown/zookeeperTools.md#jepsen-test) Jepsen had not found any bugs recently? We needs to redo that Jepsen test after we have a linearizability read api? etcd had paid for Kyle by fund from CNCF :) ----- Original Message ----- From: Michael Han <[email protected]> To: [email protected] Subject: Re: Jepsen.io report Date: 2020-02-18 14:02
I believe the original report for ZooKeeper https://aphyr.com/posts/291-call-me-maybe-zookeeper was done by the author of Jepsen. Some of the conclusions were not very accurate (see https://github.com/jepsen-io/jepsen/issues/399 - "insumity" was an intern in my team fyi). Would be nice if we can integrate Jepsen as part of apache zookeeper CI. On Sat, Feb 15, 2020 at 11:19 PM Enrico Olivelli <[email protected]> wrote: > Hi community, > I see that Jepsen.io has a very old analysis of Zookeeper (2013) > > https://jepsen.io/analyses > > Did they do by themselves or did any company pay for such analysis? > > Do you have experience in using such tools? > > > Enrico >
