zeppelin
Web-based notebook that enables data-driven, interactive data analytics and collaborative documents with SQL, Scala and more.
Runssource: GitHubhomepageJavaApache-2.0commit 703fe6763f6f
Java, Apache-2.0 licensed. The project labels itself: big data, database, flink, java, javascript, nosql, scala and spark.
zeppelin runs. An Argusic agent installed it in 54 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Apache Zeppelin 0.13.0-SNAPSHOT Java backend builds from source, all 9 server test classes pass (49 tests, 0 failures), and the embedded Jetty server starts on port 8080 responding to REST API calls with Shiro authentication active.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 97.3 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- zeppelin-web-angular npm postinstall fails: `playwright install --with-deps` needs root for system dependencies2 minutes
- JDK 11 not installed in container (no java binary found)1 minute
- zeppelin-distribution depends on zeppelin-web-angular WAR which was skipped0.5 minutes
- Lucene write.lock from previous server run blocks new start0.5 minutes
- python command not found (only python3 available), causing NotebookRestApiTest to fail0.5 minutes
- Install time
- 54 minutes
- Cold machine to finish
- 55 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- curl -s http://127.0.0.1:8080/api/version returned 200 with {"body":{"version":"0.13.0-SNAPSHOT"}}; ./mvnw test -pl zeppelin-interpreter --am ran 132/132 passed; ./mvnw test -pl zeppelin-server --am ran NotebookRestApiTest 26/26 passed
- Model tokens used
- 190,561
- Exact commit tested
- 703fe6763f6f
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exec /bin/sh -lc 'export JAVA_HOME=/tmp/jdk-11.0.26+4 && export PATH="/home/runner/bin:$JAVA_HOME/bin:$P… succeeded in 0ms: Python 3.12.3 openjdk version "11.0.26" 2025-01-21 OpenJDK Runtime Environment Temurin-11.0.26+4 (build 11.0.26+4) OpenJDK 64-Bit Server VM Temurin-11.0.26+4 (build 11.0.26+4, mixed mode) /bin/sh: 1: mvnw: not found All Java modules build, server starts on port 8080 and responds to API calls, and the full test sui… tokens used 190,561 All Java modules build, server starts on port 8080 and responds to API calls, and the full test sui…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Took 54 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
Of the 4 big-data projects Argusic has installed and timed, zeppelin was the 4th fastest to reach a running state, and 4 of 4 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/zeppelin)Questions
- Does zeppelin run?
- Yes. zeppelin runs. Argusic installed and launched it on a clean machine in 54 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test zeppelin?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 703fe6763f6f. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test zeppelin?
- The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does zeppelin take to install?
- 54 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does zeppelin need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing zeppelin?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does zeppelin compare with the alternatives?
- Of the 4 big-data projects Argusic has installed and timed, zeppelin was the 4th fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for zeppelin?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.