SQL Statements for Controlling Replica Servers source server. The same restriction applies to replacing or restoring other replicas that use ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS on any channel. For further restrictions and information, see Section 17.1.3.6, “Replication From a Source Without GTIDs to a Replica With GTIDs” . GET_SOURCE_PUBLIC_KEY Enables RSA key pair-based password exchange by requesting the public key from the source. This option applies to replicas that authenticate with the  caching_sha2_password  authentication plugin. For connections by accounts that authenticate using this plugin, the source does not send the public key unless requested, so it must be requested or specified in the client. If  SOURCE_PUBLIC_KEY_PATH is given and specifies a valid public key file, it takes precedence over  GET_SOURCE_PUBLIC_KEY . If you are using a replication user account that authenticates with the  caching_sha2_password plugin (which is the default from MySQL 8.0), and you are not using a secure connection, you must specify either this option or the SOURCE_PUBLIC_KEY_PATH  option to provide the RSA public key to the replica. IGNORE_SERVER_IDS Makes the replica ignore events originating from the specified servers. The option takes a comma-separated list of 0 or more server IDs. Log rotation and deletion events from the servers are not ignored, and are recorded in the relay log. When global transaction identifiers (GTIDs) are used for replication, transactions that have already been applied are automatically ignored, so the  IGNORE_SERVER_IDS  function is not required and is deprecated. If  gtid_mode=ON is set for the server, a deprecation warning is issued if you include the  IGNORE_SERVER_IDS 2763 Note If  IGNORE_SERVER_IDS  contains the server’s own ID and the server was started with the  --replicate-same-server-id  option enabled, an error results. In circular replication, the originating server normally acts as the terminator of its own events, so that they are not applied more than once. Thus, this option is useful in circular replication when one of the servers in the circle is removed. Suppose that you have a circular replication setup with 4 servers, having server IDs 1, 2, 3, and 4, and server 3 fails. When bridging the gap by starting replication from server 2 to server 4, you can include  IGNORE_SERVER_IDS = (3)  in the CHANGE REPLICATION SOURCE TO  statement that you issue on server 4 to tell it to use server 2 as its source instead of server 3. Doing so causes it to ignore and not to propagate any statements that originated with the server that is no longer in use.