You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 27f9b07
Browse filesBrowse the repository at this point in the historyBrowse files
fix(session): recover a runtime that crashed during suspension
Why: when a worker is lost while the Actor suspends after a turn, for example
during a node drain or scale-down, the Actor ends CRASHED and the Session still
reads READY. The idle worker keeps the suspension's claim because the outcome
is unknown, and nothing takes the claim over on a timeout. Every later send
waits out the 10-second busy period and is told to retry, so the conversation
never recovers, even with automatic recovery on. Only a crash recovery retires
the claim.
Reservation now reports a held suspension claim as ErrDispatchSuspending, a
kind of ErrDispatchBusy. requireSettledRuntime's other callers still see
ErrFailedPrecondition. With automatic recovery on, a send whose wait ends on
that claim, which a healthy suspension does not reach, attempts the bounded
recovery once. It then reserves again without waiting. Clients still get
ErrSendNotAccepted, so with the flag off nothing changes.
Reproduced on kind before and after: the worker was deleted while the Actor
was SUSPENDING. Before the fix, every send waited 10 seconds and was refused,
still stuck after six minutes. After it, the first send recovered the Session,
including one left stuck from the earlier run, and was answered.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: Ada Lundhe <[email protected]>
0 commit comments