quickwit-oss / quickwit-oss/quickwit
Return a 5xx status code when local disk is full
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
If you run quickwit and run out of disk space when ingesting, you get a rather confusing set of logs being produced and a 429 status code returned.
This is confusing if you're a user trying to debug why every request you now send is being rate limited regardless of the amount of time spent waiting.
It would be a good idea to explicitly raise a 5xx error so the client knows that something is actively wrong that cannot be retried, although running out of disk space should be rare.
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 by tracing the ingestion path and its error handling for local disk-full failures, focusing on where the current 429 response is produced. Confirm the resulting client-visible status is a 5xx and that the existing confusing logs are covered by the relevant tests, if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100