quickwit-oss / quickwit-oss/quickwit
better error when s3 is dysfunctional
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Is your feature request related to a problem? Please describe.
currently a quickwit with an S3 metastore will fail immediately if it can't reach the metastore, but it looks like it works if the metastore is working (for instance because it's postgresql) but the index_root_uri is S3 and not functional (in my case, wrong IP somewhere). However when trying to push a split, things like Directory kill switch was activated are the main messages you get, nothing obviously related to S3 being broken.
Describe the solution you'd like
clear error on startup if S3 seems to not work (because it's unreachable, the credentials are wrong, or anything else)
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 Quickwit startup handling for an S3 index_root_uri and how S3 connectivity failures surface when pushing a split. Reproduce the issue with an unreachable S3 endpoint, then verify that unreachable storage or invalid credentials produce a clear startup error instead of a later directory kill-switch message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, rust
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100