IntroductionMySQL replication slave features a powerful
capability of ignoring conflicts like duplicate key error, key
not found errors etc. while applying row events. This is
exceptionally useful while doing row based replication(RBR) from
the master when the slave already contains some data which may
conflict with the data coming from the master. In MySQL 5.7 we
extend this capability while applying row events from
mysql-binlog files using mysqlbinlog tool. This enhancement
will prevent such errors from aborting mysql client in case of
conflicts like the ones mentioned above.

RationalePrior to MySQL 5.7 we have been using the mysqlbinlog
tool as follows.

shell$> mysqlbinlog master.000001|mysql -uroot
-hexample.com -ps3cret

This allows us to pipe the output of mysqlbinlog to mysql, and
works as long as the row events from the mysqlbinlog do not
conflict with …

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.