"Snowflake users worldwide experienced serious problems this week after a recent update introduced errors in the data warehouse platform. The failed software change temporarily disabled important functions, preventing customers from running queries, loading data, and causing error messages. The cause was a database schema change that proved to be backward incompatible. This created version conflicts between different parts of the Snowflake platform, leading to failed or severely delayed operations."
"According to The Register, the outage had a global impact and affected ten of the twenty-three Snowflake regions. In the United States, this included Azure in Virginia and AWS in Oregon, while European and Asian regions, including Ireland, London, Zurich, Sweden, Mumbai, and Singapore, also experienced problems. The Register reports that Snowflake indicated it had identified the cause about an hour and a half after the first reports."
Snowflake experienced a widespread outage after a backward-incompatible database schema change created version conflicts across the platform. The change temporarily disabled key functions, preventing queries, data loads, and producing error messages. The first problems began around 02:55 UTC and in some regions lasted more than 13 hours. Ten of twenty-three regions were affected across the United States, Europe, and Asia. Snowflake identified the cause about an hour and a half after initial reports, with partial recovery by 05:00 UTC in some regions while others took longer and remained unstable. Users criticized the slow rollback. Snowflake pledged a full root cause analysis.
Read at Techzine Global
Unable to calculate read time
Collection
[
|
...
]