Demystifying MySQL Replication Crash Safety

on YouTube ↗48m

" summary

Covers concrete failure modes and exact configs that break or restore replication crash safety in MySQL 5.5–8.0: 5.5 is unsafe; 5.6 adds relay_log_info_repository=TABLE plus relay_log_recovery=1 to be safe; 5.7 relaxes defaults but GTID needs sync_binlog=1 and still needs relay_log_recovery; 8.0 ships safer defaults but changing params can remove safety. Shows how OS vs server crashes lose binlogs/relaylogs, why multi‑threaded slaves and GTID introduce races, and gives practical recovery workarounds.

AI-written summary · about

" chapters (8)

1. 0:00Start
2. 1:56Overview of Replication
3. 2:55How Does Replication Work in My Sequel
4. 4:11Replication Crash Safety
5. 20:55Global Transaction Id
6. 27:12Failure Modes
7. 32:13Multi-Threaded Replication
8. 37:30Conclusion

" related talks

• 49mMySQL Replication — Advanced FeaturesPetr Zaytsev · HighLoad++ 2017
• 14mThe State of the Art of MySQL ReplicationRicky Setyawan · FOSSASIA Summit 2017
• 22mMySQL Replication: Latest DevelopmentsSujatha Sivakumar · FOSSASIA Summit 2017
• 43mHow MySQL Replication WorksAndrey Aksenov · HighLoad++ 2014
• 53mMySQL replication setup, benefits, limitationsRick Golba, Stephane Combaudon · Percona Live MySQL Conference & Expo 2015
• 41mAsynchronous Replication Without CensorshipOleg Tsarev · HighLoad++ 2014
• 54mThe Evolution of a MySQL Database, From a Single Instance to HA With Disaster RecoveryFrederic Descamps · Percona Live 2022
• 29mEverything You Ever Wanted to Know About MariaDB Replication but Were Afraid to AskEdward Stoever · MariaDB OpenWorks 2023