In a MySQL 5.7 master-slave setup that uses the default semisynchronous replication setting for rpl_semi_sync_master_wait_point, a crash of the master and failover to the slave is considered to be lossless. However, when the crashed master comes back, you may find that it has transactions that are not present in the current master (which was previously a slave). This behavior may be puzzling, given that semisynchronous replication is supposed to be lossless, but this is actually an expected behavior in MySQL. Why exactly this happens is explained in full detail in the …
[Read more]
Showing entries 1 to 1
Dec
09
2019
Posted by ScaleGrid.io
on Mon 09 Dec 2019 20:53 UTC
Tags:
Tags:
Backup, database, cloud, High Availability, Developer, howto, binary logs, mysql replication, data integrity, restore, master-slave, backup snapshot, mysql Database, MySQL, replica set, MySQL GTID, semisynchronous replication, MySQL Hosting, ScaleGrid, Failover Process, Automated Tools, Crashed Master, Crashed MySQL, Data Inconsistency, Detect Extra Transactions, Extra Transactions, Failed Transaction, Fix Transactions, GTID_SUBSET, MySQL Master Server, New MySQL Master, Recovered Master, Recovered MySQL, Replication Error, Restore the Data
Showing entries 1 to 1
Top Authors
Joshua Otwell (12)Frederic Descamps (5)
Michael McLaughlin (4)
Alena Subotina (3)
Kristian Köhntopp (2)
Marco Tusa (2)
RoseHosting (2)
Shahryar Ghazi (2)
Chandan Kumar (1)
Daniel Nichter (1)
Evert Pot (1)
Ivan Ma (1)
Jean-François Gagné (1)
Kasra Madadipouya (1)
Kedar Vaijanapurkar (1)
Olivier Dasini (1)