quickwit-oss / quickwit-oss/quickwit
error spawning ingestion pipeline
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
hey
im setting up a qw deployment on gke. im getting a bunch of these errors
2025-07-16T23:47:36.105Z INFO spawn_pipeline{index=log_events gen=0}: quickwit_indexing::actors::indexing_pipeline: spawning indexing pipeline index_id="log_events" source_id="_ingest-api-source" pipeline_uid=01K0ASP9EJ7EC0SXA4T0GQ4RY2 root_dir=/quickwit/qwdata/indexing/log_events%01K05GZNBV00A99DEN3CZV1HKE%_ingest-api-source%01K0ASP9EJ7EC0SXA4T0GQ4RY2%5bZ6SR
2025-07-16T23:47:36.108Z ERROR quickwit_indexing::actors::indexing_pipeline: error while spawning indexing pipeline, retrying after some time error=failed to create source `_ingest-api-source` of type `ingest API v1`. Cause: internal error: could not find checkpoint for index `log_events:01K05GZNBV00A99DEN3CZV1HKE` and source `_ingest-api-source`; cause: ``
Caused by:
internal error: could not find checkpoint for index `log_events:01K05GZNBV00A99DEN3CZV1HKE` and source `_ingest-api-source`; cause: `` retry_count=8 retry_delay=512s
i literally haven't ingested anything yet, but it's causing my pods to constantly restart. i havent been able to find any other reports of this error so im looking for an explanation of what the error means and how i can fix it
thx
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 GKE deployment context and the spawn_pipeline and indexing-pipeline log entries in the report. Trace the ingest API v1 source creation and checkpoint lookup for log_events, then determine why a missing checkpoint causes repeated retries and pod restarts. Done means the cause and a verified fix or workaround are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, kubernetes, rust
- Domain
- cloud, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100