Drain accepted jobs without hanging process shutdown
Shutdown closes submissions but waits forever for a worker blocked on an external test double that never returns.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Graceful shutdown · Recovery · State machines
Estimated field mix
- Systems programming70%
- Site reliability30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional image-indexing utility runs CPU-only synthetic jobs through a Rust worker pool. Its prototype loses wakeups, blocks shutdown, and treats cancellation as completion. Build a local library and deterministic concurrency harness; image content, GPU work, and production deployment are excluded.
Setup prerequisites
- Mutexes and condition variables
- Atomics
- Thread lifecycle
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- SCONCUR-101 · Define queue ownership before starting worker threads
- SCONCUR-102 · Reject work when the bounded queue is full
- SCONCUR-103 · Close the lost-wakeup gap between predicate and sleep
- SCONCUR-104 · Keep cancellation distinct from successful completion
- SCONCUR-106 · Remove a lock-order inversion in completion reporting
Acceptance criteria
- Shutdown defines stop-accepting, drain, cancel, and terminal states
- A deadline reports unfinished job identities without detaching live threads
- Repeated shutdown calls return the same terminal outcome
Implementation constraints
- Use controlled local jobs; do not kill threads or the host process to simulate recovery.
Verification to include
- Drain a pool whose jobs complete before the deadline.
- Block one job past the deadline and confirm bounded return with an unresolved record.
Deliverables
- Shutdown protocol and stuck-job test
Rollout and recovery
Callers keep the old process exit path until they handle unresolved shutdown results.
Value of the work
For the engineer: Practice happens-before reasoning, ownership transfer, cancellation and liveness testing.
For the team: Review a worker primitive whose overload and shutdown behavior are predictable before it supports build or media workloads.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.