EC
3117
MySQLWARNINGNotableReplicationHIGH confidence

gtid_purged was changed

Production Risk

Medium — incorrect gtid_purged values can cause replication gaps.

What this means

The gtid_purged system variable was successfully changed. This is an informational warning that the value was updated.

Why it happens
  1. 1SET @@GLOBAL.gtid_purged was executed and succeeded.
  2. 2Typically seen in replication setup or after a backup restore.
How to reproduce
trigger — this will error
trigger — this will error
SET @@GLOBAL.gtid_purged = 'server-uuid:1-100';

expected output

Warning (Code 3117): The transaction owned gtid set is not empty.

Fix

Verify the new gtid_purged value is correct

Verify the new gtid_purged value is correct
SELECT @@GLOBAL.gtid_purged;

Why this works

Confirms the gtid_purged value matches expectations.

What not to do

✕

Sources
Official documentation ↗

MySQL 8.0 — 3117 ER_GTID_PURGED_WAS_CHANGED2

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

← All MySQL errors