<p>The server found a GTID_log_event in the binary log while global GTID_MODE is OFF, causing replication to halt.</p>
<p>MySQL Error 1784 ER_FOUND_GTID_EVENT_WHEN_GTID_MODE_IS_OFF__UNUSED appears when the server reads a GTID_log_event but @@GLOBAL.GTID_MODE is OFF. Enable GTID_MODE or purge the GTID events from the binlog to resume replication.</p>
Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.
Error 1784 occurs when the MySQL server encounters a GTID_log_event in a binary log file while the global variable GTID_MODE is set to OFF. Because GTID events require GTID_MODE = ON, the server stops processing the log to prevent data inconsistency.
The error blocks replication startup, point-in-time recovery, and some logical backup operations. Fixing it quickly is essential to restore replica lag and ensure a consistent recovery path.
The error shows up during CHANGE MASTER TO, START SLAVE, mysqlbinlog replay, or server startup after crash recovery. Any operation that reads a binlog containing GTID_log_event while GTID_MODE is OFF will fail with code 1784.
Replication stoppage increases fail-over time and may cause data staleness. Backups relying on mysqlbinlog cannot continue. Turning GTID_MODE back on or cleaning the offending log ensures business continuity.
An administrator disabled GTID_MODE on the primary but old binlogs still contain GTID events.
The instance was downgraded to a version that defaults to GTID_MODE = OFF while retaining binlogs from a GTID-enabled period.
A new replica was initialized from a snapshot taken when GTID_MODE was ON, but the replica’s my.cnf forces GTID_MODE = OFF.
Point-in-time recovery playback hits a GTID event although the recovery server has GTID disabled.
Occurs when GTID_PURGED is altered while replication is running.
Raised when the server cannot write to the error log during GTID recovery.
A generic replication I/O thread failure, often triggered by corrupted or mismatched binlogs.
Yes. Use the ON_PERMISSIVE phase to avoid downtime, then move to ON.
RESET MASTER only removes binary logs on the primary. Ensure backups exist before purging.
No, but GTID simplifies fail-over and recovery. Mixing modes leads to errors like 1784.
Galaxy highlights GTID variables in session status and warns when executing GTID statements on GTID disabled servers.
.avif)
.avif){kind=logo}
