Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 35.1Mb
PDF (A4) - 35.2Mb
Man Pages (TGZ) - 256.4Kb
Man Pages (Zip) - 361.2Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
Excerpts from this Manual

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

16.2.2.2 Compatibility with Previous Replication Statements

When a replica has multiple channels and aFOR CHANNELchannel option is not specified, a valid statement generally acts on all available channels, with some specific exceptions.

For example, the following statements behave as expected for all except certain Group Replication channels:

  • START SLAVE starts replication threads for all channels, except thegroup_replication_recovery andgroup_replication_applier channels.

  • STOP SLAVE stops replication threads for all channels, except thegroup_replication_recovery andgroup_replication_applier channels.

  • SHOW SLAVE STATUS reports the status for all channels, except thegroup_replication_applier channel.

  • FLUSH RELAY LOGS flushes the relay logs for all channels, except thegroup_replication_applier channel.

  • RESET SLAVE resets all channels.

Warning

UseRESET 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 1964Multiple 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 aFOR CHANNELchannel 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.