quickwit-oss / quickwit-oss/quickwit
GCS allows only 1 write/s per key
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Per GCS documentation, we may not write an object more than once a second. For most objects, we never write more than once, but for the metastore, we may update it more frequently than that, which causes errors. We should make sure we retry in this case, and that we don't increment error metrics if the retry succeeded
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
Locate the Rust code that writes the metastore to GCS and the related error metric; first inspect how write failures are classified and retried. Reproduce or test repeated writes against the GCS path, and consider the work done when a one-write-per-second violation is retried successfully without an error metric increment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, rust
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100