[
https://issues.apache.org/jira/browse/KUDU-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18121169#comment-18121169
]
ASF subversion and git services commented on KUDU-2609:
-------------------------------------------------------
Commit 63a8252e2805cff4426f854d0e65f9cd7aca146b in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=63a8252e2 ]
[kudu-jepsen] remove kudu-jepsen Java sub-project
The kudu-jepsen Java sub-project hasn't been maintained for several
years already, and there hasn't been much demand or interest in
reviving it so far. All Gradle's tasks for the sub-project's were
effectively no-op with [1] (circa October 2020).
There was an alternative changelist posted for review at [2] to catch
kudu-jepsen up to the recent jepsen and clojure versions. However,
the automation piece was still missing, so it required maintaining
several pre-provisioned nodes/VMs to run the testbench.
Eventually, after digesting review feedback for [2] and a few rounds
of offline discussions, the consensus arrived to the decision: drop
the jepsen-based sub-project from the Kudu's upstream repo.
If necessary, it's possible to restore and refresh it from the repo
when there is interest in providing more coverage for data consistency
guarantees in Kudu.
With this update, perhaps we'll need to close KUDU-2036, KUDU-2034,
and KUDU-2609 with "Won't Fix" resolution.
[1] https://github.com/apache/kudu/commit/41a7c4e4e
[2] https://gerrit.cloudera.org/#/c/24867/
Change-Id: I3bd19411c8b032c326ba992d6ce83e38426ff66e
Reviewed-on: http://gerrit.cloudera.org:8080/24876
Reviewed-by: Marton Greber <[email protected]>
Tested-by: Marton Greber <[email protected]>
> Dockerize kudu-jepsen tests
> ---------------------------
>
> Key: KUDU-2609
> URL: https://issues.apache.org/jira/browse/KUDU-2609
> Project: Kudu
> Issue Type: Improvement
> Components: jepsen, test
> Reporter: Alexey Serbin
> Assignee: Sandish Kumar HN
> Priority: Major
> Labels: newbie, test
>
> As described in {{$KUDU_ROOT/java/kudu-jepsen/README.adoc}}, current setup
> for Kudu Jepsen tests requires running those against pre-provisioned Debian
> Linux machines. As of now, it's possible to use
> {{$KUDU_ROOT/src/kudu/scripts/jepsen.sh}} in various scripted scenarios
> (e.g., Jenkins jobs) to build everything from source and run the kudu-jepsen
> tests. However, that script doesn't do any provisioning and assumes that
> Jepsen DB and control nodes are already provisioned and running.
> It would be nice to leverage Docker support for Jepsen (see
> [https://github.com/jepsen-io/jepsen/tree/master/docker] as a starting point)
> and make it possible to run kudu-jepsen tests in a dockerized environment.
> Ideally, it should be possible to run the kudu-jepsen tests at Linux (of any
> supported flavor) and macOS developer's machines as just another set of
> tests. All necessary steps should be scripted and automated. That would help
> to spot relevant issues when updating Java code in kudu-client other related
> sub-projects.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
