How to skip the LOST_EVENTS error on the MySQL Slave?
(Doc ID 1325383.1)
Last updated on JUNE 14, 2018
Applies to:MySQL Cluster - Version 6.3 and later
Information in this document applies to any platform.
You are geographically replicating your MySQL Cluster to another Cluster and your slave MySQL server received the LOST_EVENTS event. This happens because on the master side, the MySQL doing binary logging stopped and it will probably miss updates while not running. The slave MySQL server stops so some action may be taken e.g. checking consistency of data and/or switching replication channel. However, there are situations where you just want the slave MySQL server to continue replication, ignoring the LOST_EVENTS event.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!