automatically after the cloning operation when the channel is started. You do not need to perform any manual setup if you just want to use these same channels. 

•For binary log file position based replication, if the recipient is at MySQL 8.0.17 or 8.0.18, the binary log position from the donor is not applied on the recipient, only recorded in the Performance Schema clone_status  table. Replication channels on the recipient that use binary log file position based replication must therefore be set up manually to resume replication after the cloning operation. Ensure that these channels are not configured to start replication automatically at server startup, as they do not yet have the binary log position and attempt to start replication from the beginning. 

•For binary log file position based replication, if the recipient is at MySQL 8.0.19 or above, the binary log position from the donor is applied on the recipient. Replication channels on the recipient that use binary log file position based replication automatically attempt to carry out the relay log recovery process, using the cloned relay log information, before restarting replication. For a single- threaded replica ( slave_parallel_workers  is set to 0), relay log recovery should succeed in the absence of any other issues, enabling the channel to resume replication with no further setup. For a multithreaded replica ( slave_parallel_workers  is greater than 0), relay log recovery is likely to fail because it cannot usually be completed automatically. In this case, an error message is issued, and you must set the channel up manually. 

4. If you need to set up cloned replication channels manually, or want to use different replication channels on the recipient, the following instructions provide a summary and abbreviated examples for adding a recipient MySQL server instance to a replication topology. Also refer to the detailed instructions that apply to your replication setup. 

•To add a recipient MySQL server instance to a MySQL replication topology that uses GTID-based transactions as the replication data source, configure the instance as required, following the instructions in Section 17.1.3.4, “Setting Up Replication Using GTIDs” . Add replication channels for the instance as shown in the following abbreviated example. The CHANGE REPLICATION SOURCE TO  statement (from MySQL 8.0.23) or CHANGE MASTER TO  statement (before MySQL 8.0.23) must define the host address and port number of the source, and the SOURCE_AUTO_POSITION  | MASTER_AUTO_POSITION  option should be enabled, as shown: 

mysql> CHANGE MASTER TO MASTER_HOST = ’ source_host_name ’, MASTER_PORT = source_port_num , ... MASTER_AUTO_POSITION = 1, FOR CHANNEL ’ setup_channel ’; mysql> START SLAVE USER = ’ user_name ’ PASSWORD = ’ password ’ FOR CHANNEL ’ setup_channel ’; Or from MySQL 8.0.22 and 8.0.23: mysql> CHANGE SOURCE TO SOURCE_HOST = ’ source_host_name ’, SOURCE_PORT = source_port_num , ... SOURCE_AUTO_POSITION = 1, FOR CHANNEL ’ setup_channel ’; mysql> START REPLICA USER = ’ user_name ’ PASSWORD = ’ password ’ FOR CHANNEL ’ setup_channel ’; 

•To add a recipient MySQL server instance to a MySQL replication topology that uses binary log file position based replication, configure the instance as required, following the instructions in Section 17.1.2, “Setting Up Binary Log File Position Based Replication” . Add replication channels for the instance as shown in the following abbreviated example, using the binary log position that was transferred to the recipient during the cloning operation: 

mysql> SELECT BINLOG_FILE, BINLOG_POSITION FROM performance_schema.clone_status; mysql> CHANGE MASTER TO MASTER_HOST = ’ source_host_name ’, MASTER_PORT = source_port_num , ... MASTER_LOG_FILE = ’ source_log_name ’, MASTER_LOG_POS = source_log_pos , FOR CHANNEL ’ setup_channel ’; 

