Why Mysqldump Backup With GTID Replication Statements Not Applied To Other Slave? (Doc ID 1610938.1)

Last updated on FEBRUARY 06, 2017

Applies to:

MySQL Server - Version 5.6 and later
Information in this document applies to any platform.

Goal

How to make sure that a backup generated by mysqldump in a GTID enabled replication setup does not contain statements which stop binary logging or break replication ?

On a GTID enabled replication, the backup produced by mysqldump from another mysql instance (which is also running GTID replication was applied),and the sql in the dump was not passed to the slave which causes the replication to break.

The export file contains the statements :-



Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms