Migrating MariaDB Cluster to ARM
summary
MariaDB on ARM runs production packages and the migration path is concrete: add ARM nodes to a Galera cluster or restore replicas with mariabackup, use ProxySQL for LB; MaxScale is not yet available. Benchmarks show 2.2–2.5x more cores for the same cost and roughly ~50% cost saving for equal TPS. End-to-end stacks (OS, Docker/K8s, Percona Toolkit, PMM) work and ARM nodes generally scale better than x86 when deployed correctly.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:21About Krunal
- 0:52Agenda
- 3:10MariaDB on ARM
- 5:00Ecosystem
- 6:39Why consider migration
- 7:05Motivation behind migration
- 9:55How to migrate
- 10:18Other components
- 11:03Multimaster migration
- 11:40Challenges
- 13:24Alternative
- 14:04Master Slave
- 14:25Extra Replica
- 15:05Start directing queries
- 15:39Switch over again
- 16:12Migrating to ARM
- 16:32Open issues
- 16:43Considerations
- 19:58Closing
related talks
30mMySQL Ecosystem on ARM
12mMariaDB at Percona
25mThe future of databases: Combining operational and analytical data at massive scale
27mIntroduction to Configuring and Using MariaDB MaxScale: Database Proxy Made Simple
38mRunning MySQL & MariaDB Server securely in 2019
41mMariaDB The New MySQL
45mThe MariaDB Evolution: Just a fork of MySQL?
17mState of MariaDB