quickwit-oss / quickwit-oss/quickwit
Add mechanism to disable retries on failure
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
https://github.com/quickwit-inc/quickwit/issues/124 adds a retry mechanism, but as mentioned in https://github.com/quickwit-inc/quickwit/issues/124#issuecomment-885579170, there are scenarios when we don't want to retry, to avoid to DDOS ourselves.
Generally there are two approaches
- The nodes handle autonomous and retrieve the cluster information themselves.
- There is a supervisor, which activates the feature flags for retry on the nodes.
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 reading issue #124 and the referenced comment to understand the existing retry mechanism and the scenarios where retries should be disabled. The issue presents two architectural approaches but names no files, tests, or entry points. Work is done when the project has a decided mechanism for disabling retries and its behavior is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100