agent-substrate / agent-substrate/substrate
Stalled SUSPENDING actors have no system-driven recovery
オープン
area/api
area/api-machinery
area/reliability
kind/bug
- 主要言語
- Go
- スター
- 1.8k
- フォーク
- 316
- 平均マージ
- 2日 43分
- マージ済み PR（30日）
- 287
説明
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
コントリビューションガイド
評価
この issue はまだ評価されていません。