oxidecomputer / oxidecomputer/omicron
Instances stuck in starting after instance create overload
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
I ran 30 instance creations (with start) on london and got several of them to get stuck in starting.
Each instance creation has one crucible disks and 10 local storage disks.
The crucible disk is from an already created snapshot.
The 10 local storage disks are all of size 42949672960 (40GiB)
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 reproducing the reported workload: 30 instance creations in London, each with one snapshot-backed Crucible disk and ten 40 GiB local storage disks. Trace why some instances remain in starting; done means identifying the overload failure and preventing instances from becoming permanently stuck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100