MySQL at Scale: Booking MariaDB to MySQL Migration
summary
Booking migrates by replacing replication chains rather than in‑place upgrades, building a new MySQL chain, seeding it with mydumper + storage copy‑on‑write cloning and using a 96‑core 120TB server on steroids as a temporary primary. The process handles thousands of servers, takes about 3–4 months for execution, exposes schema incompatibilities like nullable composite primary keys and timestamp defaults, and requires disabling durability features and close coordination with application fixes.
AI-written summary · about
chapters (6)
related talks
50mMySQL/MariaDB Parallel Replication: inventory, use cases and limitations
21mSwitching from MySQL/Percona to MariaDB
29mEverything You Ever Wanted to Know About MariaDB Replication but Were Afraid to Ask
19mMove to the Cloud with Zero Downtime
16mMigrating from other databases to MariaDB
41mMariaDB The New MySQL
57mThe Evolution of a MySQL Database System
34mMySQL 8