oxidecomputer / oxidecomputer/omicron
Revisit Backoff Policy
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
There have been several issues with long backoffs recently.
- #3082
- #3165
As an interim solution to these problems, and in light of the fact that we are focused on single rack deployments at the moment, a PR is coming in that reduces the maximum backoff interval from 60 minutes to 3 minutes. However, we need to revisit the topic of backoff more broadly. Making sure that the mechanism we ultimately use works in service of both snappy and scalable deployments.
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 reviewing issues #3082 and #3165, then inspect the incoming PR that reduces the maximum backoff interval from 60 minutes to 3 minutes. The broader work is done when a backoff mechanism is defined that supports both snappy and scalable deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100