DataOperationalEnvironment scoped
Durability
Committed changes append to a durable history and batch into object storage.
Instances4Placed in the selected environment
Replica freshness9 / 129 of 12 copies current
Regions3Holding a copy of this environment
In flight2Runtime work running right now
What it guarantees
An instance keeps its live state in memory while the write-ahead history is the durable copy. A dormant instance comes back from its latest closed state plus the log records after it.
- Hold state durably without an attached volume to provision
- Batch history uploads so object requests stay affordable
- Bring an instance back on demand after it goes dormant or moves
Configured resources
What this capability is holding up in the environment in scope right now.
| Resource | Kind | State | Configuration |
|---|---|---|---|
| production-history | Storage prefix | Active | Closed state and batched log segments |
| history compactor | Durability worker | Active | Compacts recoverable state |
| rehydration cache | Runtime cache | Ready | Recent state near active servers |
Telemetry
Unapplied history0 bytesEvery closed segment is uploaded
Upload p9586 msTo the configured store
Newest upload11 seconds agoIn the selected environment
Recent activity
- History batch uploadedCompleted, 1 minute agoThe latest write-ahead batch reached object storage.
- Dormant instance restoredObserved, 7 minutes agoinventory/sku-188 came back from stored state and two log segments.