Renew a scheduler lease only for the current holder and epoch
A delayed renewal from an earlier process extends the newest owner's lease row while reporting success to the stale process.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Guarded updates · Lease renewal
Estimated field mix
- Distributed systems70%
- Database engineering30%
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 document service runs periodic retention planning on multiple application instances. Paused instances resume after lease expiry and can overlap newer schedulers.
Setup prerequisites
- Create a synthetic maintenance queue and two independent scheduler clients.
- Use fake time where possible and no destructive real retention actions.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- ALEASE-101 · Specify scheduler lease state with a separate authority epoch
- ALEASE-102 · Use one authoritative clock boundary for lease decisions
- ALEASE-103 · Classify maintenance actions that require fencing before side effects
- ALEASE-104 · Acquire a scheduler lease atomically under competing instances
Acceptance criteria
- Match holder instance and epoch in the renewal update.
- Bound extension duration from the authoritative clock.
- Return lost authority when no matching active lease exists.
Implementation constraints
- Never renew solely by a shared scheduler name.
Verification to include
- Renew the current owner successfully.
- Acquire a newer epoch, then submit the old renewal and reject it.
Deliverables
- Guarded renewal and stale-message test
Rollout and recovery
Enable guarded renewal before automated scheduling; make authority loss stop further work claims.
Value of the work
For the engineer: Practice lease assumptions, fencing and stale-owner rejection.
For the team: Review safe coordination that remains explainable under pauses and recovery.
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.