Author

Sunil Pai <spai@cloudflare.com> 2026-02-18 14:18:13 +0000

Parents

1ba05cb

Tree

910452f

Store Durable Object alarms per-namespace on disk

Previously, all alarms were stored in a single global in-memory SQLite
database, meaning they were lost on process restart. This made it
impossible to test alarm resiliency scenarios.

Move alarm scheduler ownership from Server into ActorNamespace, so each
DO namespace gets its own AlarmScheduler backed by metadata.sqlite in
the namespace's storage directory. On-disk namespaces get persistent
alarms; in-memory namespaces get in-memory alarms. No new configuration
is needed -- alarm storage follows the existing durableObjectStorage
setting.

Ref: https://github.com/cloudflare/workerd/pull/605#issuecomment-1542469018
Co-authored-by: Cursor <cursoragent@cursor.com>