You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "maoling (JIRA)" <ji...@apache.org> on 2019/02/23 10:55:00 UTC

[jira] [Commented] (ZOOKEEPER-2704) Run Jepsen against branch-3.5 / master of ZooKeeper

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775852#comment-16775852 ] 

maoling commented on ZOOKEEPER-2704:
------------------------------------

Mark it, it could not be better that the Jepsen can be integrated with the CI.

> Run Jepsen against branch-3.5 / master of ZooKeeper
> ---------------------------------------------------
>
>                 Key: ZOOKEEPER-2704
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2704
>             Project: ZooKeeper
>          Issue Type: Sub-task
>          Components: tests
>    Affects Versions: 3.5.2
>            Reporter: Michael Han
>            Priority: Major
>              Labels: test
>             Fix For: 3.6.0
>
>
> The [Jepsen report|https://aphyr.com/posts/291-jepsen-zookeeper] on ZooKeeper was using an old version of ZooKeeper (3.4.5). It would be good to run Jepsen on trunk / branch-3.5 and see what happens. This will also give our confidence on the quality of the upcoming 3.5 stable release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)