When set, each channel purges its own relay log automatically. 

• --slave_transaction_retries 

The specified number of transaction retries can take place on all applier threads of all channels. 

• --skip-slave-start  (or skip_slave_start  system variable set) 

No replication threads start on any channels. 

• --slave-skip-errors 

Execution continues and errors are skipped for all channels. 

The values set for the following startup options apply on each channel; since these are mysqld  startup options, they are applied on every channel. 

• --max-relay-log-size= size 

Maximum size of the individual relay log file for each channel; after reaching this limit, the file is rotated. 

• --relay-log-space-limit= size 

Upper limit for the total size of all relay logs combined, for each individual channel. For N  channels, the combined size of these logs is limited to relay_log_space_limit * N . 

• --slave-parallel-workers= value 

Number of replication applier threads per channel. 

• slave_checkpoint_group 

Waiting time by an I/O thread for each source. 

• --relay-log-index=filename 

Base name for each channel’s relay log index file. See Section 17.2.2.4, “Replication Channel Naming Conventions” . 

• --relay-log=filename 

Denotes the base name of each channel’s relay log file. See Section 17.2.2.4, “Replication Channel Naming Conventions” . 

• --slave_net-timeout=N 

This value is set per channel, so that each channel waits for N  seconds to check for a broken connection. 

• --slave-skip-counter=N 

This value is set per channel, so that each channel skips N  events from its source. 

## 17.2.2.4 Replication Channel Naming Conventions 

This section describes how naming conventions are impacted by replication channels. 

Each replication channel has a unique name which is a string with a maximum length of 64 characters and is case-insensitive. Because channel names are used in the replica’s applier metadata repository table, 

