Query: 'DROP TABLE `example`.`accounts` /* generated by server */' | 23:57:52 | | main | 1 | NULL | OFF | ANONYMOUS | 1051 | Worker 0 failed executing transaction 'ANONYMOUS' at master log mysql-bin.019567, end_log_pos 163723076 Error 'Unknown table 'example.accounts'' on query. | CHANNEL_NAME | WORKER_ID | THREAD_ID | SERVICE_STATE | LAST_SEEN_TRANSACTION | LAST_ERROR_NUMBER | LAST_ERROR_MESSAGE | LAST_ERROR_TIMESTAMP | Check the status of replication with detailed messages in the table performance_schema.replication_applier_status_by_worker through select * from the table: mysql> select * from performance_schema.replication_applier_status_by_worker The command will use the setting for global sql_slave_skip_counter = 1 to skip one statement and start slave on that channel (for example ‘main’) by: starting slave for channel ‘channel-name’ start slave for channel 'main' ġ.4: Start slave on all the other channels by: start slave start slave 2. How can we make sure the global sql_slave_skip_counter is applied to a specific channel and not to the other channel? Here are the steps:ġ.1: Stop all slaves by: stop slave stop slave ġ.2: Set up the count of statement to skip by: SET GLOBAL sql_slave_skip_counter = N SET GLOBAL sql_slave_skip_counter = 1 ġ.3: Start slave on the channel we want to skip the statement on. We need to be very careful not to skip the statement from the other channel, since the command SET GLOBAL sql_slave_skip_counter = N is for global. Sometimes, we might find out that one of the channels stop replication due to some error, and we may want to skip the statement for that channel so that we can restart a slave for it. Here is a list of some operation tips for the convenience of use as below: 1. With support of multi-threads replication starting from MySQL 5.7, the operations on slave are slightly different from single-thread replication.

Mysql skip counter 1