My Oracle Support Banner

Binary Log Events are Looping Between Servers In Source-Source Or Circular Replication (Doc ID 1663900.1)

Last updated on JANUARY 04, 2022

Applies to:

MySQL Server - Version 5.6 and later
Information in this document applies to any platform.

Symptoms

Disclaimer: Starting from v8.0, some terms have been deprecated. Older releases will only use the deprecated terminology, and new releases will only use new terminology. Please see https://dev.mysql.com/doc/mysqld-version-reference/en/ for a complete list of those changes, and in which minor versions it happened.

A MySQL server which is part of a circular or source-source 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).

Changes

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. 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
 MySQL 5.6 or later
 MySQL 5.5 or earlier
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.