Configure Replication Failover with MariaDB Xpand
This page is part of MariaDB's MariaDB Documentation.
The parent of this page is: Configure Replication with MariaDB Xpand
Topics on this page:
A common high availability (HA) configuration for MariaDB is the Master/Master pair. In such a configuration, each side is both a Slave and a Master. The application can write to only one instance at a time (Active/Passive) or to both instances (Active/Active). Assuming you are familiar with MariaDB replication configuration and management, you can Configure Master-Master Replication wth MariaDB Xpand for this purpose.
If you using MySQL 5.7 or higher, please see Configure MariaDB Xpand as a Replication Master and Configure MariaDB Xpand as a Replication Slave for information on GTIDs.
MariaDB Xpand 5.3
MariaDB Xpand 6.0
MariaDB Xpand 6.1
Configuring MySQL-to-Xpand Replication in Master/Master
This section tells you how to make a MySQL Master a Slave to the Xpand system. Prerequisites:
Configure Xpand to generate MySQL binary logs.
Create a replication user on the MySQL Master server.
Ensure that Xpand and MySQL have unique values for global server_
Assuming that Xpand is configured as a Slave to an existing MySQL Master, you can configure MySQL as a Slave to the Xpand system. To prevent undesired "write" actions on the Xpand Slave from being replicated to the Master MySQL instance, put Xpand into a read-only mode by issuing the following command. Any updates coming through the binary log bypass read-only:
slave> SET GLOBAL read_only = true;
You now have an Active/Passive replication topology, with Xpand acting as the Passive (Slave) system.
Promoting a Xpand Slave to Master
Before promoting, ensure that the Passive Slave is keeping up with the replication stream from the Active Master. Verify that the Passive Slave is not more than a couple of seconds behind the Active Master by issuing the
SHOW SLAVE STATUS command. If the Slave is significantly behind, wait for it to catch up, to reduce the amount of time required for the replication network to quiesce. Verify that the MySQL Active Master is replicating from the Xpand Passive Slave instance.
To quiesce the system and get the Active and Passive systems into a known consistent state, disable writes to the MySQL Active Master by issuing the following command:
master> SET GLOBAL read_only = true;
To determine the active MySQL Master's position, issue the following command:
master> SHOW MASTER STATUS\G
When the two systems display the same position, they are in a consistent and quiescent state. Now you can safely promote either system to the role of Active Master.
To promote a Xpand Passive Slave to Active Master, disable read-only mode on Xpand by issuing the following command:
slave> SET GLOBAL read_only = false;
Next, redirect the application to use the Xpand system as its write target. The Xpand system is now configured as the Active Master. Verify that events are getting replicated to the MySQL server, which is now configured as the Passive Slave.
When Xpand is the Active Master, you can obtain information about all the slaves connected to the master by issuing the following command:
master> SHOW FULL processlist;
To easily identify the slave(s), a best practice is to use user names that end with "_
To promote a Xpand Slave (Passive) to a Master (Active) replication participant, perform the following steps:
Put the current MySQL Master instance into read-only mode and wait for the Xpand Slave instance to catch up.
Disable read-only mode on the Xpand Slave (if it is enabled).
Migrate application traffic.