Dissecting GitHub Outage - Downtime due to ALTER TABLE



1694 views Outage Dissections



Can an ALTER TABLE command take down your production? 🤯

It happened to GitHub on 27th November 2021 when most of their services were down because of a large schema migration.

Why did the outage happen?

GitHub ran a migration on a massive MySQL table and it made their replicas enter deadlock and crash. Here are the 5 insights about their architecture

Insight 1: Schema migration can take weeks to complete

Schema migrations are intense operations as in most cases require you to copy the entire table with the new schema. Hence it might take a schema migration weeks to complete.

Insight 2: The last step of migration is RENAME

To protect the database from not taking excessive locks during the migration, we create an empty ghost table from the main table, apply migration, copy the data, and then rename the table. This reduces the locks we need for the migration.

Insight 3: Read Replicas can have deadlocks

The writes happening through the replication job and the production read load can create deadlocks on the read replicas.

Insight 4: Have a separate fleet of replicas for internal traffic

Have a separate fleet of Read Replicas for internal workflows ex: analytics, etc. This way, any internal load will not affect the production load.

Insight 5: Database failures cascade

When a replica fails, the load on healthy one’s increases; which may them down and hence the cascading effect.

Mitigation

The outage happened because there were not enough read replicas to handle the load, hence in order to mitigate it the way out was to add more read replicas. GitHub team very smartly promoted the replicas used for internal workloads to handle production.

Although the move was smart, it did not mitigate the outage because the incoming load was so high that the new replicas added also started crashing.

Data Integrity over Availability

To ensure that the data integrity is not compromised because of repeated crashes, GitHub took a call and let the Read traffic fail. They took the replica out of the production fleet, gave it time to complete the migration, and then added it back.

This way all the replicas got the time they needed to complete the schema migration. It took some but the issue was completely mitigated.

Long-term fix

Vertical Partitioning is a long-term fix for this problem. The idea is to create smaller databases that hold related tables; ex: all tables related to Repositories can go in one DB. This allows migration to quickly complete and during an outage, only the involved functionalities will be affected.


Arpit Bhayani

Arpit's Newsletter

CS newsletter for the curious engineers

❤️ by 14000+ readers

If you like what you read subscribe you can always subscribe to my newsletter and get the post delivered straight to your inbox. I write essays on various engineering topics and share it through my weekly newsletter.




Other videos that you might like


Dissecting GitHub Outage: Downtime due to an Edge Case

838 views 41 likes 2022-05-23

In August 2021, GitHub experienced an outage where their MySQL Master database went into a degraded state. Upon investig...

Dissecting GitHub Outage - Downtime due to ALTER TABLE

1694 views 88 likes 2022-05-09

Can an ALTER TABLE command take down your production? 🤯 GitHub had a major outage and it all started with a schema migr...

An engineering deep-dive into Atlassian's Mega Outage of April 2022

4303 views 226 likes 2022-04-15

In April 2022, Atlassian suffered a major outage where they "permanently" deleted the data for 400 of their paying cloud...

Dissecting Google Maps Outage: Bad Rollout and Cascading Failures

1104 views 69 likes 2022-04-01

Google Maps had a global outage on 18th March 2022, during which the end-users were not able to use Directions, Navigati...


Arpit's Newsletter read by 14000+ engineers

🔥 Thrice a week, in your inbox, an essay about system design, distributed systems, microservices, programming languages internals, or a deep dive on some super-clever algorithm, or just a few tips on building highly scalable distributed systems.



  • v10.6.4
  • © Arpit Bhayani, 2022