SQL Statements for Controlling Replica Servers To use  RESET REPLICA | SLAVE , the replication SQL thread and replication I/O thread must be stopped, so on a running replica use  STOP REPLICA | SLAVE  before issuing  RESET REPLICA | SLAVE . To use  RESET REPLICA | SLAVE  on a Group Replication group member, the member status must be  OFFLINE , meaning that the plugin is loaded but the member does not currently belong to any group. A group member can be taken offline by using a  STOP GROUP REPLICATION  statement. The optional  FOR CHANNEL  channel  clause enables you to name which replication channel the statement applies to. Providing a  FOR CHANNEL  channel  clause applies the  RESET REPLICA | SLAVE statement to a specific replication channel. Combining a  FOR CHANNEL  channel  clause with the  ALL option deletes the specified channel. If no channel is named and no extra channels exist, the statement applies to the default channel. Issuing a  RESET REPLICA | SLAVE ALL  statement without a  FOR CHANNEL  channel  clause when multiple replication channels exist deletes  all  replication channels and recreates only the default channel. See Section 17.2.2, “Replication Channels”  for more information. RESET REPLICA | SLAVE  does not change any replication connection parameters, which include the source’s host name and port, the replication user account and its password, the  PRIVILEGE_CHECKS_USER  account, the REQUIRE_ROW_FORMAT  option, the  REQUIRE_TABLE_PRIMARY_KEY_CHECK  option, and the ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS   option. If you want to change any of the replication connection parameters, you can do this using a  CHANGE REPLICATION SOURCE TO  statement (from MySQL 8.0.23) or  CHANGE MASTER TO  statement (before MySQL 8.0.23) after the server start. If you want to remove all of the replication connection parameters, use  RESET REPLICA | SLAVE ALL .  RESET REPLICA | SLAVE ALL  also clears the  IGNORE_SERVER_IDS  list set by  CHANGE REPLICATION SOURCE TO  |  CHANGE MASTER TO . When you have used  RESET REPLICA | SLAVE ALL , if you want to use the instance as a replica again, you need to issue a  CHANGE REPLICATION SOURCE TO  |  CHANGE MASTER TO  statement after the server start to specify new connection parameters. In the event of an unexpected server exit or deliberate restart after issuing  RESET REPLICA | SLAVE  but before issuing  START REPLICA | SLAVE , retention of the replication connection parameters depends on the repository used for the replication metadata: •When  master_info_repository=TABLE  and  relay_log_info_repository=TABLE are set on the server (which are the default settings from MySQL 8.0), replication connection parameters are preserved in the crash-safe  InnoDB  tables  mysql.slave_master_info  and mysql.slave_relay_log_info  as part of the  RESET REPLICA | SLAVE  operation. They are also retained in memory. In the event of an unexpected server exit or deliberate restart after issuing RESET REPLICA | SLAVE  but before issuing  START REPLICA | SLAVE , the replication connection parameters are retrieved from the tables and reapplied to the channel. This situation applies from MySQL 8.0.13 for the connection metadata repository, and from MySQL 8.0.19 for the applier metadata repository. •If  master_info_repository=FILE  and  relay_log_info_repository=FILE  are set on the server, which is deprecated from MySQL 8.0, or the MySQL Server release is earlier than those specified above, replication connection parameters are only retained in memory. If the replica  mysqld is restarted immediately after issuing  RESET REPLICA | SLAVE  due to an unexpected server exit or deliberate restart, the connection parameters are lost. In that case, you must issue a  CHANGE REPLICATION SOURCE TO  statement (from MySQL 8.0.23) or  CHANGE MASTER TO  statement (before MySQL 8.0.23) after the server start to respecify the connection parameters before issuing  START REPLICA | SLAVE . RESET REPLICA | SLAVE  does not change any replication filter settings (such as  --replicate- ignore-table ) for channels affected by the statement. However,  RESET REPLICA | SLAVE ALL removes the replication filters that were set on the channels deleted by the statement. When the deleted channel or channels are recreated, any global replication filters specified for the replica are copied to them, and no channel specific replication filters are applied. For more information see Section 17.2.5.4, “Replication Channel Based Filters” . 2774