CONCEPT Cited by 1 source
Errant GTID tracking¶
Definition¶
An errant GTID (Global Transaction ID) is a transaction that exists on a replica but not on the primary of a MySQL replication topology — it was committed to the replica without having been replicated from the primary, which means the replica's data has diverged from the primary's authoritative history. Errant GTIDs arise from misconfigurations (writes to a read-only replica that weren't actually read-only), failover mishaps, or split-brain scenarios. They are a precursor to correctness incidents because any subsequent reparent decision must reconcile them (either by declaring the errant GTID lost, replaying it on the new primary, or refusing the reparent). Errant GTID tracking is the operational discipline of counting errant GTIDs across a replication topology as a fleet-wide health metric, so operators can alert on divergence before a reparent decision forces the reconciliation.
Seen in¶
- sources/2026-04-21-planetscale-announcing-vitess-21 — Vitess 21 adds a new metric in VTOrc that shows the count of errant GTIDs in all the tablets: "This will help operators track and manage errant GTIDs across the cluster." Canonical wiki datum for errant-GTID operational visibility as the precursor metric that fires before a reparent decision is needed.