oxidecomputer / oxidecomputer/crucible
Support inflight IO upstairs migration
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
The current migration for crucible upstairs involves deactivation then activation of a fresh new upstairs.
This requires inflight IOs to be completed (at the deactivation step).
Crucible should support migration of in memory data structures over to the new upstairs and allow it to continue accepting IOs it had sent from the downstairs.
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 tracing the current Crucible upstairs migration, including the deactivation and fresh-upstairs activation steps. Identify the in-memory data structures and inflight IO lifecycle involved. Done means migration preserves the required state on the new upstairs and allows previously sent IOs to complete while new IOs continue to be accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100