
The option's value can be specified by providing a comma-separated list of
server_id values. For example:

STOP SLAVE;
CHANGE MASTER TO 
 IGNORE_SERVER_IDS = (3,5);
START SLAVE;

If you would like to clear a previously set list, then you can set the value
to an empty list. For example:

STOP SLAVE;
CHANGE MASTER TO 
 IGNORE_SERVER_IDS = ();
START SLAVE;

DO_DOMAIN_IDS
-------------

The DO_DOMAIN_IDS option for CHANGE MASTER can be used to configure a replica
to only apply binary log events if the transaction's GTID is in a specific
gtid_domain_id value. Filtered binary log events will not get logged to the
replica’s relay log, and they will not be applied by the replica.

The option's value can be specified by providing a comma-separated list of
gtid_domain_id values. Duplicate values are automatically ignored. For example:

STOP SLAVE;
CHANGE MASTER TO 
 DO_DOMAIN_IDS = (1,2);
START SLAVE;

If you would like to clear a previously set list, then you can set the value
to an empty list. For example:

STOP SLAVE;
CHANGE MASTER TO 
 DO_DOMAIN_IDS = ();
START SLAVE;

The DO_DOMAIN_IDS option and the IGNORE_DOMAIN_IDS option cannot both be set
to non-empty values at the same time. If you want to set the DO_DOMAIN_IDS
option, and the IGNORE_DOMAIN_IDS option was previously set, then you need to
clear the value of the IGNORE_DOMAIN_IDS option. For example:

STOP SLAVE;
CHANGE MASTER TO 
 IGNORE_DOMAIN_IDS = (),
 DO_DOMAIN_IDS = (1,2);
START SLAVE;

The DO_DOMAIN_IDS option can only be specified if the replica is replicating
in GTID mode. Therefore, the MASTER_USE_GTID option must also be set to some
value other than no in order to use this option.

IGNORE_DOMAIN_IDS
-----------------

The IGNORE_DOMAIN_IDS option for CHANGE MASTER can be used to configure a
replica to ignore binary log events if the transaction's GTID is in a specific
gtid_domain_id value. Filtered binary log events will not get logged to the
replica’s relay log, and they will not be applied by the replica.

The option's value can be specified by providing a comma-separated list of
gtid_domain_id values. Duplicate values are automatically ignored. For example:

STOP SLAVE;
CHANGE MASTER TO 
 IGNORE_DOMAIN_IDS = (1,2);
START SLAVE;

If you would like to clear a previously set list, then you can set the value
to an empty list. For example:

STOP SLAVE;
CHANGE MASTER TO 
 IGNORE_DOMAIN_IDS = ();
START SLAVE;

The DO_DOMAIN_IDS option and the IGNORE_DOMAIN_IDS option cannot both be set
to non-empty values at the same time. If you want to set the IGNORE_DOMAIN_IDS
option, and the DO_DOMAIN_IDS option was previously set, then you need to
clear the value of the DO_DOMAIN_IDS option. For example:

STOP SLAVE;
CHANGE MASTER TO 
 DO_DOMAIN_IDS = (),
 IGNORE_DOMAIN_IDS = (1,2);
START SLAVE;

The IGNORE_DOMAIN_IDS option can only be specified if the replica is
replicating in GTID mode. Therefore, the MASTER_USE_GTID option must also be
set to some value other than no in order to use this option.

Delayed Replication Options
---------------------------

MASTER_DELAY
------------

The MASTER_DELAY option for CHANGE MASTER can be used to enable delayed
replication. This option specifies the time in seconds (at least) that a
replica should lag behind the primary up to a maximum value of 2147483647, or
about 68 years. Before executing an event, the replica will first wait, if
necessary, until the given time has passed since the event was created on the
primary. The result is that the replica will reflect the state of the primary
some time back in the past. The default is zero, no delay.

STOP SLAVE;
CHANGE MASTER TO 
 MASTER_DELAY=3600;
START SLAVE;

Changing Option Values
----------------------

If you don't specify a given option when executing the CHANGE MASTER
statement, then the option keeps its old value in most cases. Most of the
time, there is no need to specify the options that do not need to change. For
example, if the password for the user account that the replica uses to connect
to its primary has changed, but no other options need to change, then you can
just change the MASTER_PASSWORD option by executing the following commands:

STOP SLAVE;
CHANGE MASTER TO 
 MASTER_PASSWORD='new3cret';
START SLAVE;

There are some cases where options are implicitly reset, such as when the
MASTER_HOST and MASTER_PORT options are changed.

Option Persistence
------------------

The values of the MASTER_LOG_FILE and MASTER_LOG_POS options (i.e. the binary
log position on the primary) and most other options are written to either the
default master.info file or the file that is configured by the
master_info_file option. The replica's I/O thread keeps this binary log
position updated as it downloads events only when MASTER_USE_GTID option is
set to NO. Otherwise the file is not updated on a per event basis.

The master_info_file option can be set either on the command-line or in a
server option group in an option file prior to starting up the server. For
example:

[mariadb]
...
master_info_file=/mariadb/myserver1-master.info

The values of the RELAY_LOG_FILE and RELAY_LOG_POS options (i.e. the relay log
position) are written to either the default relay-log.info file or the file
that is configured by the relay_log_info_file system variable. The replica's
SQL thread keeps this relay log position updated as it applies events.
