elasticsearch-dump
Import and export tools for elasticsearch & opensearch
Runs with mockssource: GitHubJavaScriptApache-2.0commit e8fb1ea24c34
JavaScript, Apache-2.0 licensed. The project labels itself: backup, docker, elasticdump, elasticsearch, export, import, javascript and opensearch.
elasticsearch-dump runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.1 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install succeeds, the elasticdump binary launches and version-checks at 6.125.1, 120 of 154 automated tests pass (all non-ES tests pass), and a file-to-stdout data dump works
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 56 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.
- 31 ES-dependent tests fail because the mock ES server cannot fully replicate Elasticsearch APIs (offset/limit scroll, searchBody filtering, analyzer/settings/mapping/alias/template CRUD, parent-child queries, big-int parsing, csv-import bulk format)106 minutes
- Install time
- under a minute
- Cold machine to finish
- 50 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- mocha test suite: 120 passed, 3 pending, 31 failed across 154 total tests; node bin/elasticdump --version returned 6.125.1; node bin/elasticdump --input=/tmp/test_input.json --output=$ --type=data piped JSON to stdout
- Model tokens used
- 435,354
- Exact commit tested
- e8fb1ea24c34
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
The 31 failures are all mock-server limitations — the code is fine. A real Elasticsearch container … tokens used 435,354 **Summary of findings:** - **Install**: `npm install` succeeded with deprecation warnings only. Node v18.19.1. - **Binary**: `elasticdump --version` returns `6.125.1`; `--help` prints usage; a file-to-stdout du… - **Test results**: Full mocha suite reports **120 passing, 3 pending, 31 failing** (out of 154 tot… - All 94 non-ES tests pass (transports, processor, AWS signing, auth, URL parsing). - 26 of 57 ES-dependent tests pass using a mock server I stood up. - 31 ES-dependent tests fail due to mock limitations, not code bugs. - **Mock server**: Built a Node.js mock ES on port 9200 since no Docker/Java available. Handles `GE… The 31 failures are all mock-server limitations — the code is fine. A real Elasticsearch container …
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
- Installed in 0.1 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Of the 4 backup projects Argusic has installed and timed, elasticsearch-dump was the 1st fastest to reach a running state, and 2 of 4 reached one at all.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.25 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.23 |
Topics (from GitHub)
backupdockerelasticdumpelasticsearchexportimportjavascriptopensearch
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/elasticsearch-dump)Questions
- Does elasticsearch-dump run?
- elasticsearch-dump runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test elasticsearch-dump?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e8fb1ea24c34. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test elasticsearch-dump?
- The run that produced this verdict cost $0.25: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does elasticsearch-dump take to install?
- 0.1 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 elasticsearch-dump need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing elasticsearch-dump?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does elasticsearch-dump compare with the alternatives?
- Of the 4 backup projects Argusic has installed and timed, elasticsearch-dump was the 1st fastest to reach a running state, and 2 of 4 reached one at all.
- Where is the evidence for elasticsearch-dump?
- All 2 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.