Scribd
Upload
4 views3 pages

MySQL Replication

Replication ensures that data is copied to secondary servers for redundancy and administrative purposes. It includes methods such as Standard Asynchronous Replication, which completes transactions locally before logging them for slaves, and Semi-Synchronous Replication, which requires acknowledgment from slaves before proceeding. Group Replication, introduced in MySQL 5.7, allows for virtual synchronous replication by achieving consensus among nodes before completing transactions.

Uploaded by

Siva Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
4 views3 pages

MySQL Replication

Replication ensures that data is copied to secondary servers for redundancy and administrative purposes. It includes methods such as Standard Asynchronous Replication, which completes transactions locally before logging them for slaves, and Semi-Synchronous Replication, which requires acknowledgment from slaves before proceeding. Group Replication, introduced in MySQL 5.7, allows for virtual synchronous replication by achieving consensus among nodes before completing transactions.

Uploaded by

Siva Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Replication:

Replication guarantees information gets copied and purposely populated into another
environment, instead of only stored in one location.

The idea is to use secondary servers on your infrastructure for either reads or other
administrative solutions. The below diagram shows an example of a MySQL replication
environment.

Standard Asynchronous Replication

Asynchronous replication means that the transaction is completed on the local environment
completely and is not influenced by the replication slaves themselves.

After completion of its changes, the master populates the binary log with the data
modification or the actual statement (the difference between row-based replication or
statement-based replication – more on this later). The slave executes each change on the
slave’s database using the SQL thread.
Semi-Synchronous Replication

Semi-synchronous replication means that the slave and the master communicate with each
other to guarantee the correct transfer of the transaction. Semi-synchronous replication
guarantees that a transaction is correctly copied, but it does not guarantee that the commit on
the slave actually takes place.

Important to note is that semi-sync replication makes sure that the master waits to continue
processing transactions in a specific session until at least one of the slaves has ACKed the
reception of the transaction (or reaches a timeout).

Keep in mind that semi-synchronous replication impacts performance because it needs to


wait for the round trip of the actual ACK from the slave.
Group Replication

This is a new concept introduced in the MySQL Community Edition 5.7, and was GA’ed in
MySQL 5.7.17. It’s a rather new plugin build for virtual synchronous replication.

Whenever a transaction is executed on a node, the plugin tries to get consensus with the other
nodes before returning it completed back to the client. Although the solution is a completely
different concept compared to standard MySQL replication, it is based on the generation and
handling of log events using the binlog.

Below is an example architecture for Group Replication.

Note:

We recommend to you configure Master-Slave replication with Standard Asynchronous


Replication

You might also like