Red Hat Enterprise Linux6.464-bit MySQL5.6 master-slave Replication

This article introduces the application in the production environment through master-slave replication of MySQL5.6 on the 64-bit System Platform of Red Hat RedHat6.4, GTID-based replication, semi-synchronization, SSL encryption, and read/write splitting., let's share it with you. Mysql5.6 Master-Slave replication introduces the Slave server to connect to the Master through the IO thread, and requests to Start copying from the specified log. The Master returns the name of its BinaryLog file and the position and inner letter in the BinaryLog.

This article introduces the configuration application in the production environment through master-slave replication of MySQL 6.4 On the 64-bit System Platform of Red Hat RedHat 5.6, GTID-based replication, semi-synchronization, SSL encryption, and read/write splitting. practical, let's share it with you.

Mysql5.6 master-slave Replication

The Slave server connects to the Master through an IO thread and requests replication starting from the specified Log. The Master returns the name of its Binary Log file and the location and content information in the BinaryLog, the Slave end saves the copied log information to its own relay log, and then executes the event information in the relay log one by one locally to store the data locally.

Master-slave replication Architecture

Introduction to semi-synchronous replication of Mysql5.6

In one Master-Slave mode, only one Slave synchronization replication is completed between the Master and Slave (consistent with the Master-Slave replication mechanism). That is, the thread that commits the transaction is locked, it is not until at least one Slave receives this transaction that the transaction event is sent to the Slave after it is committed to the storage engine.

Semi-sync architecture of Mysql5.6 master-slave mode

The principle section is introduced in batches here. Let's take a look at the implementation process of Mysql replication.