Bug #78467 mysqldump --dump-slave does not work with multi-source
Submitted: 17 Sep 2015 11:46 Modified: 23 May 2016 15:13
Reporter: Sven Sandberg Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: mysqldump Command-line Client Severity:S3 (Non-critical)
Version:5.7 OS:Any
Assigned to: CPU Architecture:Any

[17 Sep 2015 11:46] Sven Sandberg
Multi-source replication was introduced in 5.7.
Now, there may be multiple masters, each replicating through its own channel.
Configuration for individual channels is specified using CHANGE MASTER TO ... FOR CHANNEL 'channel-name';
For backward compatibility, there always exists a 'default' channel, having channel name ''.

Even if multi-source replication is enabled, mysqldump --dump-slave outputs only a single CHANGE MASTER statement, setting the positions only for the default channel.

How to repeat:

Suggested fix:
In the presence of multiple channels, mysqldump --dump-slave should output one CHANGE MASTER statement for each replication channel.
[23 May 2016 15:13] David Moss
The following was added to the 5.7.13 changelog:
mysqldump has been updated to make it compatible with multi-source replication. Now when replication channels other than the default channel are found, mysqldump --dump-slave outputs a CHANGE MASTER TO statement for each replication channel.