quickwit-oss / quickwit-oss/quickwit
Corrupt split after merge
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
I am running git sha 2025-09-21T06:01:37.990Z INFO quickwit_cli::service: quickwit version: 0.8.0 (x86_64-unknown-linux-gnu 2025-09-12T14:57:53Z ef6b319)
and keep running into data corruption
Error: { "message": "internal error: `search failed for the following splits: 01K5NF8E7YF6C5SM8HT3BQZ9BY. For instance, split 01K5NF8E7YF6C5SM8HT3BQZ9BY failed with the following error message: internal error: `spawned task in root join failed: task 2455 panicked with message \"assertion failed: end <= orig_range.end\"``" }
this happens after a split is merged. The indexer and metastore believe the split was fine and if I query the split via describe util, I dont see a problem but search fails. This is happening no matter if I reset the index.
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
Reproduce the failure on Quickwit 0.8.0 using the reported merged split and search error. Start with the split merge path, the indexer and metastore state, and the describe utility, then trace the end <= orig_range.end assertion. Done means merged splits remain searchable without the panic or corruption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100