GTID replication has made it convenient to setup and maintain MySQL replication. You need not worry about binary log file and position thanks to GTID and auto-positioning. However, things can go wrong when pointing a slave to a different master. Consider a situation where the new master has executed transactions that havent been executed on [&]

The post Fixing ER_MASTER_HAS_PURGED_REQUIRED_GTIDS when pointing a slave to a different master appeared first on Percona Database Performance Blog.

https://www.percona.com/blog/2018/07/02/fixing-er_master_has_purged_required_gtids-when-pointing-a-slave-to-a-different-master/