Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 37.2Mb
PDF (A4) - 37.2Mb
PDF (RPM) - 36.9Mb
EPUB - 10.5Mb
HTML Download (TGZ) - 10.3Mb
HTML Download (Zip) - 10.3Mb
HTML Download (RPM) - 8.9Mb
Eclipse Doc Plugin (TGZ) - 11.1Mb
Eclipse Doc Plugin (Zip) - 13.3Mb
Man Pages (TGZ) - 203.8Kb
Man Pages (Zip) - 309.1Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
Excerpts from this Manual

MySQL 5.7 Reference Manual  /  ...  /  Compatibility with Previous Replication Statements

18.2.3.2 Compatibility with Previous Replication Statements

When a replication slave has multiple channels and a FOR CHANNEL channel_name option is not specified, a valid statement generally acts on all available channels.

For example, the following statements behave as expected:

  • START SLAVE starts replication threads for all channels. (In MySQL 5.7.9 and later, this does not include the group_replication_recovery channel.)

  • STOP SLAVE stops replication threads for all the channels. (In MySQL 5.7.9 and later, this does not include the group_replication_recovery channel.)

  • SHOW SLAVE STATUS reports the status for all channels.

  • FLUSH RELAY LOGS flushes the relay logs for all channels.

  • RESET SLAVE resets all channels.

Warning

Use RESET SLAVE with caution as this statement deletes all existing channels, purges their relay log files, and recreates only the default channel.

Some replication statements cannot operate on all channels. In this case, error 1964 Multiple channels exist on the slave. Please provide channel name as an argument. is generated. The following statements and functions generate this error when used in a multi-source replication topology and a FOR CHANNEL channel_name option is not used to specify which channel to act on:

Note that a default channel always exists in a single source replication topology, where statements and functions behave as in previous versions of MySQL.


User Comments
Sign Up Login You must be logged in to post a comment.