Binary log events are looping between servers in master-master or circular replication
Last updated on JUNE 13, 2016
Applies to:MySQL Server - Version 5.6 and later
Information in this document applies to any platform.
A MySQL server which is part of a circular or master-master replication configuration is continuously executing the same events over and over again. They appear to be looping between the servers.
Symptoms may include binary logs growing at a fast rate, queries constantly running in the processlist as the MySQL replication system user, or replication may stop entirely with an error because an event was repeated that cannot run again (such as a DELETE or INSERT with unique ID).
A server in the setup has changed server_id. This may be due to a reconfiguration on the same host, or by migrating the MySQL instances from one node to another changing the server_id in the process.
It may also occur if you remove or otherwise bypass a replication server from the ring.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms