<p>MySQL cannot create a new GTID because the server’s integer sequence has reached its maximum value, halting transactions until the server_uuid is changed.</p>
<p>MySQL Error 1775: ER_GNO_EXHAUSTED appears when the GTID integer component is maxed out, blocking new transactions. Fix it by restarting MySQL with a fresh server_uuid or cloning the instance, then resynchronizing replication.</p>
Impossible to generate GTID: the integer component
Error 1775 signals that the signed 64-bit integer used in a server’s GTID sequence has reached its maximum value. MySQL can no longer append a new Global Transaction Identifier, so it refuses every write.
The issue surfaces on very busy replication masters or long-running servers where billions of transactions have consumed the entire integer space tied to the current server_uuid.
No new GTID means all future transactions fail with SQLSTATE HY000. Replication slaves stall and application writes return errors, causing downtime and possible data loss if not handled promptly.
The integer counter inside a GTID grows with each committed transaction. When that counter hits 263-1, it cannot increase further. MySQL therefore throws ER_GNO_EXHAUSTED and stops generating GTIDs.
High-throughput systems, constant binlog activity, stress tests, or forgotten development servers running for years can all exhaust the counter.
The only safe remedy is to assign a brand-new server_uuid so GTID numbering restarts from zero. This requires a planned restart and brief downtime. After restart, reconfigure replication as needed.
An alternate strategy is to clone the instance onto fresh hardware or a new container with a unique server_uuid, then promote it and decommission the exhausted node.
Standalone servers simply need a restart with a regenerated UUID. Primary-replica setups must also reset gtid_purged on replicas to match the new primary’s GTID set before replication resumes.
Multi-source clusters demand coordination: update any topology metadata so routers and orchestrators recognize the new server_uuid.
Enable monitoring on performance_schema.replication_applier_status_by_worker to alert when the GTID integer nears critical thresholds. Plan controlled UUID rotations long before exhaustion.
Use shorter server lifecycles by rebuilding masters periodically instead of letting them run indefinitely. Large cloud fleets often automate this rotation.
Errors 1236 (Could not find first log file) and 1620 (Binlog closed) interrupt replication for different reasons, typically missing or corrupt binlogs. They are fixed by resynchronizing replicas with a fresh snapshot, unlike ER_GNO_EXHAUSTED, which needs a new server_uuid.
Very active OLTP systems can exhaust the GTID integer within years or even months if the workload commits millions of transactions per second.
Dev or staging servers left running for a decade may slowly consume the entire counter even at low TPS.
Accidental circular replication can multiply GTID generation and burn through the sequence rapidly.
Without alerts on GTID exhaustion percentage, administrators miss early warnings and discover the problem only after writes fail.
Occurs when the replica’s replication position references a purged or missing binary log. Fixed by copying fresh backups and resetting the master log file.
Happens when the binary log closes unexpectedly, often after disk issues. Restarting MySQL and re-enabling binlog solves it.
Indicates corruption inside relay logs on a replica. Use CHANGE MASTER TO RELAY_LOG_FILE to skip the bad event or rebuild the replica.
Compare the integer part of the latest GTID in performance_schema.gtid_executed with 9223372036854775807. Alert at 90 percent.
Switching off gtid_mode stops new GTID writes but breaks replication consistency. It is not recommended in production.
RESET MASTER removes the binlog history but keeps the current server_uuid, so the counter is still exhausted. You must assign a new UUID.
Galaxy’s monitoring panel surfaces GTID statistics and alerts engineers when counters approach limits, letting teams schedule proactive maintenance.
.avif)
.avif){kind=logo}
