Syntax\n------\n\nRESET { SLAVE | REPLICA } ["connection_name"] [ALL]  [FOR CHANNEL "connection_name"].\n\nDescription\n-----------\n\nRESET SLAVE makes the slave forget its replication position in the master's binary log. This statement is meant to be used for a clean start. It deletes the master.info and relay-log.info files, all the relay log files, and starts a new relay log file. To use RESET SLAVE, the slave threads must be stopped (use STOP SLAVE if necessary).\n\nNote: All relay log files are deleted, even if they have not been completely executed by the slave SQL thread. (This is a condition likely to exist on a replication slave if you have issued a STOP SLAVE statement or if the slave is highly loaded.)\n\nNote: RESET SLAVE does not reset the globalgtid_slave_pos variable. This means that a slave server configured with CHANGE MASTER TO MASTER_USE_GTID=slave_pos will not receive events with GTIDs occurring before the state saved ingtid_slave_pos. If the intent is to reprocess these events,gtid_slave_pos must be manually reset, e.g., by executing set global gtid_slave_pos="".\n\nConnection information stored in the master.info file is immediately reset using any values specified in the corresponding startup options. This information includes values such as master host, master port, master user, and master password. If the slave SQL thread was in the middle of replicating temporary tables when it was stopped, and RESET SLAVE is issued, these replicated temporary tables are deleted on the slave.\n\nThe ALL also resets the PORT, HOST, USER, and PASSWORD parameters for the slave. If you are using a connection name, it will be permanently deleted it and it will not show up anymore in SHOW ALL SLAVES STATUS.\n\nconnection_name\n\nThe connection_name option is used for multi-source replication.\n\nIf there is only one nameless master, or the default master (as specified by the default_master_connection system variable) is intended, connection_name can be omitted. If provided, the RESET SLAVE statement will apply to the specified master. connection_name is case-insensitive.\n\nMariaDB starting with 10.7.0\n\nThe FOR CHANNEL keyword was added for MySQL compatibility. This is identical to using the channel_name directly after RESET SLAVE.\n\nFOR CHANNEL is not available.\n\nThe FOR CHANNEL keyword was added for MySQL compatibility. This is identical as using the channel_name directly after RESET SLAVE.\n\nMariaDB starting with 11.6.0\n\nRESET SLAVE resets the Master/Slave_last_event_time and Connects_Tried values (see SHOW SLAVE STATUS).\n\nRESET SLAVE resets the Master/Slave_last_event_time values (see SHOW SLAVE STATUS).\n\nRESET SLAVE does not reset the Master/Slave_last_event_time values (see SHOW SLAVE STATUS).\n\nURL: https://mariadb.com/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/reset-replica