Site posture
Included from Basic tier
A site posture is the durable record that a whole site is quiesced:
every server node whose configured site matches drains and holds —
offers stop, in-flight drives hand over to the other site's replicas,
and the site's stamped dispatch work falls back so it never strands.
Postures survive restarts and holds apply at boot; only the explicit,
audited resume lifts one. With a site configured, a posture read error
holds the node — site scoping fails closed.
Served by RunnerService.ListSitePostures (the response also carries
the answering node's own site identity and current held state) and
written by QuiesceSite/ResumeSite — opschain admin server site list|quiesce|resume. Every transition lands in the audit lane as
info:server:site_quiesced / info:server:site_resumed.
| Field | Type | Meaning |
|---|---|---|
site | string | The quiesced site's identity (the servers' configured site value). |
quiesced_by | string | The principal that quiesced the site. |
quiesced_at | timestamp | When the site was quiesced. |
Related
- Runner registry and fleet queue
- Admin status — carries the node's site and held state
- The server rolling-upgrade and multi-site operations runbooks shipped with the product documentation