Hi Alex, Yes, Jepsen tests of Scalar DB run as a part of the daily testing. Each of them runs for an hour every day.
However, some tests fail due to a client thread crash. It seems to be unrelated to Cassandra and Scalar DB. I think that my implementation might have a problem. Now, I'm investigating that issue. That would be a great idea if our work will be included in the regular testing drill. Thanks, Yuji 2018年11月9日(金) 17:27 Oleksandr Shulgin <oleksandr.shul...@zalando.de>: > On Thu, Nov 8, 2018 at 10:42 PM Yuji Ito <y...@phact-columba.com> wrote: > > > > > We are working on Jepsen testing for Cassandra. > > https://github.com/scalar-labs/jepsen/tree/cassandra/cassandra > > > > As you may know, Jepsen is a framework for distributed systems > > verification. > > It can inject network failure and so on and check data consistency. > > https://github.com/jepsen-io/jepsen > > > > Our tests are based on riptano's great work. > > https://github.com/riptano/jepsen/tree/cassandra/cassandra > > > > I refined it for the latest Jepsen and removed some tests. > > Next, I'll fix clock-drift tests. > > > > I would like to get your feedback. > > > > Cool stuff! Do you have jepsen tests as part of regular testing in > scalardb? How long does it take to run all of them on average? > > I wonder if Apache Cassandra would be willing to include this as part of > regular testing drill as well. > > Cheers, > -- > Alex >
