"Our initial investigation has identified that our most recent release introduced a backwards-incompatible database schema update,"
"As a result, previous release packages errantly referenced the updated fields, resulting in version mismatch errors and causing operations to fail or take an extended amount of time to complete."
"Took them way too long to role [sic] back this change"
Snowflake pushed an update that triggered a major worldwide outage, leaving many users unable to query data, failing to ingest files, and receiving error messages for up to 13 hours. The release introduced a backwards-incompatible database schema update; previous packages referenced updated fields, producing version mismatch errors that caused operations to fail or take longer. Ten of 23 global regions were affected, including Azure Virginia and AWS Oregon, plus Ireland, Zurich, London, Sweden, Mumbai, Singapore, and Mexico. Initial errors appeared at 0255 UTC; the problem was identified about 1.5 hours later and systems were restored by about 0500 UTC. A root cause analysis will be released within five days of incident closure.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]