Asynchronous Replication Automatic Failover in MySQL 8.0.22
Oracle recently released MySQL 8.0.22, and this new version came with a new asynchronous connection failover mechanism. It allows a replica to automatically establish an asynchronous replication connection to a new source, in case...
My DBA is Sick – Database Failover Tips for SysAdmins
In case of a database failure, the best case scenario is that you have a good Disaster Recovery Plan (DRP) and a highly available environment with an automatic failover process in place. But what happens...
How to Automate Database Failover with ClusterControl
Recovery Time Objective (RTO) is the time period within which a service must be restored to avoid unacceptable consequences. By calculating how long it can take to recover from a database failure, we can know...
6 Common Failure Scenarios for MySQL & MariaDB, and How to Fix Them
It this blog post, we will analyze 6 different failure scenarios in production database systems, ranging from single-server issues to multi-datacenter failover plans. We will walk you through recovery and failover procedures for the respective...
Automatic Failover of Postgres Replication
Streaming replication setups with Postgres are inevitably related to failovers. The sole writer in the setup would be the primary, it generates XLOG records and continuously ships them to one or more standby servers. If...
MySQL Replication and GTID-Based Failover – A Deep Dive Into Errant Transactions
For years, MySQL replication used to be based on binary log events - all a slave knew was the exact event and the exact position it just read from the master. Any single transaction from...
Automatic Failover of MySQL Replication – New in ClusterControl 1.4
MySQL replication setups are inevitably related to failovers. Unlike multi-master clusters like Galera, there is one single writer in a whole setup - the master. If the master fails, one of the slaves will have...
MySQL Replication Failover – MaxScale vs MHA: Part Four
In the earlier blogs in this series, we concluded that MaxScale with MariaDB Replication Manager still has some way to go as a failover solution. The failover mechanism relied on MariaDB GTID, needed a wrapper...
MySQL Replication Failoverv – Maxscale vs MHA: Part Three
In our previous two posts we described in depth how MySQL Master-HA (MHA) and MaxScale + MariaDB Replication Manager (MRM) both perform their so called slave promotions (also known as master failover). MHA has been...
MySQL Replication Failover – Maxscale vs MHA: Part Two
In our previous post, we described how MySQL Master-HA (MHA) performs a so called slave promotion (also known as master failover) and ensures all remaining slaves in the topology get attached under the new master...
MySQL Replication Failover – Maxscale vs MHA: Part One
In our MySQL replication tutorial we have covered different aspects of replication including master failover by performing a slave promotion using ClusterControl. The slave promotion will turn a slave into the new master, and re-attach...