quickwit-oss / quickwit-oss/quickwit
Lazy filed backed index error logged after index is deleted
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
After deleting an index, we see this log:
2023-03-15T23:07:31.832Z ERROR quickwit_metastore::metastore::file_backed_metastore::lazy_file_backed_index: fetch-metadata-error error=IndexDoesNotExist { index_id: "stackoverflow" }
The file-backed index metastore is trying to reload the index file, but it's no more here. We could avoid logging this error.
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 in the lazy_file_backed_index module mentioned in the log and trace the metadata reload that occurs after an index is deleted. Adjust the handling so the expected missing-index case is not logged as an error, while other metadata failures remain visible. Confirm that deleting an index no longer produces this error log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100