Error
Error Code:
1789
MariaDB Error 1789: Master Purged Required GTIDs
Description
This error indicates that a MariaDB replication slave, configured with `MASTER_AUTO_POSITION = 1` for GTID-based replication, cannot find necessary transaction information on the master server. It occurs when the master has deleted binary log files that contain GTIDs the slave needs to resume or establish its replication position. This interruption prevents the slave from catching up with the master.
Error Message
The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.
Known Causes
3 known causesShort Binary Log Retention
The master's `expire_logs_days` or `binlog_expire_logs_seconds` setting is configured too aggressively, causing binary logs to be purged before the slave can process them.
Significant Slave Lag
The replication slave has fallen considerably behind the master, requiring GTIDs from binary logs that have already been cleaned up.
Accidental Manual Purge
An administrator manually executed `PURGE BINARY LOGS` on the master server, inadvertently removing logs that the slave still needed for its replication position.
Solutions
Coming SoonDetailed step-by-step solutions for this error are being prepared. In the meantime, try these general troubleshooting tips:
General Troubleshooting Tips
- Check the error message carefully for specific details
- Review recent changes that might have caused the error
- Search for the exact error code in the official documentation
- Check log files for additional context
- Try restarting the application or service