agent-substrate / agent-substrate/substrate
Stalled SUSPENDING actors have no system-driven recovery
Aperta
area/api
area/api-machinery
area/reliability
kind/bug
- Lingua principale
- Go
- Stelle
- 1.8k
- Fork
- 316
- Merge medio
- 2g 43m
- PR unite (30g)
- 287
Descrizione
Split out of #791 (the deferred "janitor / retry budget" item) so #791 can close.
### Problem:
If `SuspendActor` fails after the actor is marked `SUSPENDING`, the actor stays `SUSPENDING` until a client calls `SuspendActor` again. In that state it cannot be resumed.
A running-origin suspend at least has a graceful termination exit: if the worker pod goes away, `DeleteWorker` marks the actor `CRASHED`.
A paused-origin is pinned to a node name, and once the node is gone every retry fails with just internal errors.
Xref: #660 #791 #817 #798
Guida per i contributori
Apri la guida per i contributori
Valutazione
Questa issue non è ancora stata valutata.