RESET {REPLICA | SLAVE} [ALL] [channel_option]
channel_option:
    FOR CHANNEL channel

RESET REPLICA | SLAVE makes the replica forget its position in the source's binary log. RESET REPLICA | SLAVE使副本忘记其在源二进制日志中的位置。From MySQL 8.0.22, use RESET REPLICA in place of RESET SLAVE, which is deprecated from that release. 在MySQL 8.0.22中，使用RESET REPLICA代替RESET SLAVE，该版本不推荐使用RESET SLAVE。In releases before MySQL 8.0.22, use RESET SLAVE.在MySQL 8.0.22之前的版本中，使用RESET SLAVE。

This statement is meant to be used for a clean start; it clears the replication metadata repositories, deletes all the relay log files, and starts a new relay log file. 本声明旨在用于一个干净的开始；它清除复制元数据存储库，删除所有中继日志文件，并启动新的中继日志文件。It also resets to 0 the replication delay specified with the SOURCE_DELAY | MASTER_DELAY option of the CHANGE REPLICATION SOURCE TO statement (from MySQL 8.0.23) or CHANGE MASTER TO statement (before MySQL 8.0.23).它还将使用CHANGE REPLICATION SOURCE TO语句（从MySQL 8.0.23开始）或CHANGE MASTER TO语句（在MySQL 8.0.23之前）的SOURCE_DELAY | MASTER_DELAY选项指定的复制延迟重置为0。

For a server where GTIDs are in use (gtid_mode is ON), issuing RESET REPLICA | SLAVE has no effect on the GTID execution history. 对于使用GTID的服务器（gtid_mode为ON），发出RESET REPLICA | SLAVE对GTID执行历史记录没有影响。The statement does not change the values of gtid_executed or gtid_purged, or the mysql.gtid_executed table. 该语句不会更改gtid_executed或gtid_purged的值，也不会更改mysql.gtid_executed表的值。If you need to reset the GTID execution history, use RESET MASTER, even if the GTID-enabled server is a replica where binary logging is disabled.如果需要重置GTID执行历史记录，请使用RESET MASTER，即使启用GTID的服务器是禁用二进制日志记录的副本。

RESET REPLICA | SLAVE requires the RELOAD privilege.RESET REPLICA | SLAVE需要RELOAD权限。

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. 要使用RESET REPLICA | SLAVE，必须停止复制SQL线程和复制I/O线程，因此在运行的副本上，在发出RESET REPLICA | SLAVE之前使用STOP 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. 要在组复制组成员上使用RESET REPLICA | SLAVE，成员状态必须为OFFLINE（脱机），这意味着插件已加载，但该成员当前不属于任何组。A group member can be taken offline by using a STOP GROUP REPLICATION statement.可以使用STOP GROUP REPLICATION语句使组成员脱机。

The optional FOR CHANNEL channel clause enables you to name which replication channel the statement applies to. 可选的FOR CHANNEL channel子句允许您命名语句应用于哪个复制通道。Providing a FOR CHANNEL channel clause applies the RESET REPLICA | SLAVE statement to a specific replication channel. 提供FOR CHANNEL channel子句将RESET REPLICA | SLAVE语句应用于特定的复制通道。Combining a FOR CHANNEL channel clause with the ALL option deletes the specified channel. 将FOR CHANNEL channel子句与ALL选项组合将删除指定的通道。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. 当存在多个复制通道时，在没有FOR CHANNEL channel子句的情况下发出RESET REPLICA | SLAVE ALL语句将删除所有复制通道，并仅重新创建默认通道。See Section 17.2.2, “Replication Channels” for more information.有关更多信息，请参阅第17.2.2节，“复制通道”。

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. RESET REPLICA | SLAVE不会更改任何复制连接参数，包括源的主机名和端口、复制用户帐户及其密码、PRIVILEGE_CHECKS_USER帐户、REQUIRE_ROW_FORMAT选项、REQUIRE_TABLE_PRIMARY_KEY_CHECK选项和ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS选项。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. 如果要更改任何复制连接参数，可以在服务器启动后使用CHANGE REPLICATION SOURCE TO语句（从MySQL 8.0.23开始）或CHANGE MASTER TO语句（在MySQL 8.0.23之前）。If you want to remove all of the replication connection parameters, use RESET REPLICA | SLAVE ALL. 如果要删除所有复制连接参数，请使用RESET REPLICA | SLAVE ALL。RESET REPLICA | SLAVE ALL also clears the IGNORE_SERVER_IDS list set by CHANGE REPLICATION SOURCE TO | CHANGE MASTER TO. RESET REPLICA | SLAVE ALL还会通过CHANGE REPLICATION SOURCE TO|CHANGE MASTER TO来清除IGNORE_SERVER_IDS列表集。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.当你使用了RESET REPLICA | SLAVE ALL之后，如果你想要再次使用实例作为复本，你需要在服务器开始指定新连接参数后，发出CHANGE REPLICATION SOURCE TO|CHANGE MASTER TO。

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:如果在发出RESET REPLICA | SLAVE之后但在发出START REPLICA | SLAVE之前发生意外的服务器退出或故意重新启动，复制连接参数的保留取决于用于复制元数据的存储库：

RESET REPLICA | SLAVE does not change any replication filter settings (such as --replicate-ignore-table) for channels affected by the statement. RESET REPLICA | SLAVE不会更改受语句影响的通道的任何复制筛选器设置（例如--replicate-ignore-table）。However, RESET REPLICA | SLAVE ALL removes the replication filters that were set on the channels deleted by the statement. 但是，RESET REPLICA | SLAVE ALL将删除在该语句删除的通道上设置的复制筛选器。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”.有关更多信息，请参阅第17.2.5.4节，“基于复制通道的筛选器”。

RESET REPLICA | SLAVE causes an implicit commit of an ongoing transaction. RESET REPLICA | SLAVE导致正在进行的事务的隐式提交。See Section 13.3.3, “Statements That Cause an Implicit Commit”.请参阅第13.3.3节，“导致隐式提交的语句”。

If the replication SQL thread was in the middle of replicating temporary tables when it was stopped, and RESET REPLICA | SLAVE is issued, these replicated temporary tables are deleted on the replica.如果复制SQL线程处于停止时复制临时表的中间，并发出了RESET REPLICA | SLAV，则复制的临时表将被删除。

RESET REPLICA | SLAVE does not reset the heartbeat period or SSL_VERIFY_SERVER_CERT.RESET REPLICA | SLAVE不重置心跳周期或SSL_VERIFY_SERVER_CERT。