Changes / Dagster / Database maintenance failover

Dagster: Critical incident: Database maintenance failover

Summary

Dagster reported a critical incident starting 2023-09-18 12:46 UTC, with a computed duration of 0 min. The vendor described a 90-second disruption during cloud-provider database maintenance as a primary database failed over to a secondary; Dagster operations during that window would have failed. The incident was resolved, with all systems back to normal.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 91%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Database maintenance failover
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2023-09-18 12:46 UTC
AddedResolved time#5
Before: not present
After: 2023-09-18 12:46 UTC
AddedUpdateresolved#6
Before: not present
After: Database maintenance by our cloud provider caused a 90 second service disruption between 12:46:10 UTC and 12:47:40 UTC while a primary database failed over to a secondary. Dagster operations during this window would have failed. All systems have resumed normal operation.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Critical incident: Database maintenance failover (this change)
Dagster reported a critical incident starting 2023-09-18 12:46 UTC, with a computed duration of 0 min. The vendor described a 90-second disruption during cloud-provider database maintenance as a primary database failed over to a secondary; Dagster operations during that window would have failed. The incident was resolved, with all systems back to normal.
Major incident

All Dagster changes → · Dagster profile · Markdown · JSON