Re: make MySQL server master and slave at the same time
Skipping transaction means that the copy of your data being maintained by the slave will be incomplete compared to the copy of the data being maintained by your master.
Replication operates by duplicating the changes on one system (the master) in another system (the slave).
Let's imagine that the changes in the Binary Log that you no longer have a copy of were the INSERT of 1000 rows of data. If you skip them, your slave will be short 1000 rows of data.
You need to start over, with a fresh copy of the master so that the copy you have is consistent with some position (or GTID value) that still exists within the master's Binary Log. That's the only way to be sure you can accurately duplicate the changes that happened to the source data *after* you made the backup.
Yours,
--
Shawn Green
MySQL Senior Principal Technical Support Engineer
Subject
Views
Written By
Posted
1793
May 17, 2019 05:15AM
Re: make MySQL server master and slave at the same time
471
May 26, 2019 02:38PM
485
June 07, 2019 03:17AM
434
June 07, 2019 09:33AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.