SQL Statements for Controlling Replica Servers the list of ignored servers, it is necessary to use the option with an empty list: RESET REPLICA | SLAVE ALL  clears  IGNORE_SERVER_IDS . CHANGE MASTER TO IGNORE_SERVER_IDS = (); A deprecation warning is issued if  SET GTID_MODE=ON  is issued when any channel has existing server IDs set with IGNORE_SERVER_IDS . Before starting GTID- based replication, check for and clear all ignored server ID lists on the servers involved. The  SHOW REPLICA | SLAVE STATUS  statement displays the list of ignored IDs, if there is one. If you do receive the deprecation warning, you can still clear a list after  gtid_mode=ON  is set by issuing a  CHANGE MASTER TO  statement containing the IGNORE_SERVER_IDS  option with an empty list. Note Both the replica and the source must have GTIDs enabled ( GTID_MODE=ON ,  ON_PERMISSIVE,  or  OFF_PERMISSIVE  on the replica, and  GTID_MODE=ON  on the source).  MASTER_LOG_FILE , MASTER_LOG_POS ,  RELAY_LOG_FILE , and  RELAY_LOG_POS  cannot be specified together with  MASTER_AUTO_POSITION = 1 . If multi- source replication is enabled on the replica, you need to set the MASTER_AUTO_POSITION = 1  option for each applicable replication channel. With  MASTER_AUTO_POSITION = 1  set, in the initial connection handshake, the replica sends a GTID set containing the transactions that it has already received, committed, or both. The source responds by sending all transactions recorded in its binary log whose GTID is not included in the GTID set sent by the replica. This exchange ensures that the source only sends the transactions with a GTID that the replica has not already recorded or committed. If the replica receives transactions from more than one source, as in the case of a diamond topology, the auto-skip function ensures that the transactions are not applied twice. For details of how the GTID set sent by the replica is computed, see Section 17.1.3.3, “GTID Auto-Positioning” . If any of the transactions that should be sent by the source have been purged from the source’s binary log, or added to the set of GTIDs in the  gtid_purged  system variable by another method, the source sends the error  ER_MASTER_HAS_PURGED_REQUIRED_GTIDS  to the replica, and replication does not start. The GTIDs of the missing purged transactions are identified and listed in the source’s error log 2748 Makes the replica attempt to connect to the source using the auto- positioning feature of GTID-based replication, rather than a binary log file based position. This option can be used with  CHANGE MASTER TO only if both the replication SQL thread and replication I/O thread are stopped. MASTER_AUTO_POSITION