Replication Channels When set, each channel purges its own relay log automatically. The specified number of transaction retries can take place on all applier threads of all channels. No replication threads start on any channels. 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. Maximum size of the individual relay log file for each channel; after reaching this limit, the file is rotated. 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 . Number of replication applier threads per channel. Waiting time by an I/O thread for each source. Base name for each channel’s relay log index file. See Section 17.2.2.4, “Replication Channel Naming Conventions” . Denotes the base name of each channel’s relay log file. See Section 17.2.2.4, “Replication Channel Naming Conventions” . This value is set per channel, so that each channel waits for  N  seconds to check for a broken connection. This value is set per channel, so that each channel skips  N  events from its source. 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, 3595 17.2.2.4 Replication Channel Naming Conventions • --slave-skip-counter=N • --slave_net-timeout=N • --relay-log=filename • --relay-log-index=filename • slave_checkpoint_group • --slave-parallel-workers= value • --relay-log-space-limit= size • --max-relay-log-size= size • --slave-skip-errors • --skip-slave-start  (or  skip_slave_start  system variable set) • --slave_transaction_retries