EC
1775
MySQLWARNINGNotableReplicationHIGH confidence

gtid_purged was changed

Production Risk

Medium — replicas may lose sync if gtid_purged change is not accounted for.

What this means

The value of gtid_purged was changed on the server, which is logged as a warning because it can affect replica synchronisation.

Why it happens
  1. 1Administrator explicitly modified gtid_purged via SET GLOBAL.
  2. 2RESET MASTER was executed.
How to reproduce
trigger — this will error
trigger — this will error
SET GLOBAL gtid_purged = 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:1-100';

expected output

Warning (Code 1775): GTID_PURGED was changed from '' to 'xxxxxxxx:1-100'.

Fix

Verify replicas are aware of the new gtid_purged value

Verify replicas are aware of the new gtid_purged value
-- On replica:
SHOW SLAVE STATUS\G
-- Check Executed_Gtid_Set and Retrieved_Gtid_Set

Why this works

Ensures replicas can still connect and have not missed any transactions.

What not to do

✕

Sources
Official documentation ↗

MySQL 8.0 — 1775 ER_GTID_PURGED_WAS_CHANGED

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

← All MySQL errors