oxidecomputer / oxidecomputer/omicron
Sled Agent inventory should use some concurrency
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
As of oxidecomputer/omicron#4727, we collect inventory from sled agents. But we do it sequentially. The latency is not a huge deal, but if one sled doesn't respond for a while, it'll cork up inventory collection until it times out. If multiple don't respond, we'll wait sequentially for them to time out.
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 locating the inventory collection path introduced by oxidecomputer/omicron#4727 and trace how it queries sled agents. Check how timeouts are handled when one or more agents do not respond. Done means inventory collection no longer waits for each sled agent sequentially, while preserving the existing inventory results and timeout behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100