quickwit-oss / quickwit-oss/quickwit
Indexing twice the same file with the local ingest command generate worrying log errors
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Everything is going well, but we log some errors, and we don't know if quickwit indexed something or not.
quickwit tool local-ingest --index hdfs-logs --input-path hdfs-logs-multitenants-10000.json --config ../config/quickwit.yaml
❯ Ingesting documents locally...
---------------------------------------------------
Connectivity checklist
✔ metastore storage
✔ metastore
✔ index storage
✔ _ingest-cli-source
2024-01-16T12:12:20.675Z ERROR quickwit_actors::spawn_builder: actor-failure cause=An IO error occurred: 'No such file or directory (os error 2)' exit_status=Failure(An IO error occurred: 'No such file or directory (os error 2)')
2024-01-16T12:12:20.675Z ERROR quickwit_actors::actor_context: exit activating-kill-switch actor=MergeExecutor-delicate-6Yll exit_status=Failure(An IO error occurred: 'No such file or directory (os error 2)')
Clearing local cache directory...
✔ Local cache directory cleared.
✔ Documents successfully indexed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the quickwit tool local-ingest command using the duplicate hdfs-logs-multitenants-10000.json input and the shown ../config/quickwit.yaml. Trace the MergeExecutor and actor error output, then verify whether duplicate ingestion succeeds without misleading errors and confirm the command's final status is accurate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100