A database replication topology is never written in stone - it evolves along with your application and data. Changes are usually needed to help scale out, to distribute your database across multiple regions or data centers, or to perform software/hardware maintenance operations. The initial setup of a replication topology is simple, but as soon as you start changing it, things can quickly get complex.
How do we fail-over our replication masters and slaves without affecting the availability and consistency of our data?
In this webinar, we discuss how to perform replication topology changes in MySQL / MariaDB, and what the failover process may look like. We also discuss some external tools you may find useful when dealing with those operations.
MySQL Replication topology changes
using regular replication
Using MaxScale for automatic re-routing of queries
Other external tools useful when dealing with failover