EC
1776
MySQLWARNINGNotableReplicationHIGH confidence

gtid_executed was changed

Production Risk

High — can break replication on all replicas.

What this means

The value of gtid_executed was reset or changed, typically as a result of RESET MASTER, which is logged as a warning.

Why it happens
  1. 1RESET MASTER was executed, clearing gtid_executed.
  2. 2Administrator directly modified GTID state.
How to reproduce
trigger — this will error
trigger — this will error
RESET MASTER; -- clears gtid_executed

expected output

Warning (Code 1776): GTID_EXECUTED was changed from 'xxxxxxxx:1-100' to ''.

Fix

Reconfigure replicas after resetting gtid_executed on the primary

Reconfigure replicas after resetting gtid_executed on the primary
-- On replica:
STOP SLAVE;
RESET SLAVE;
CHANGE MASTER TO MASTER_AUTO_POSITION=1;
START SLAVE;

Why this works

Re-establishes GTID-based replication after the master GTID state was reset.

What not to do

✕

Sources
Official documentation ↗

MySQL 8.0 — 1776 ER_GTID_EXECUTED_WAS_CHANGED

Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev

← All MySQL errors