SET GLOBAL SQL_SLAVE_SKIP_COUNTER

Syntax

Description

This statement skips the next N events from the primary. This is useful for recovering from replication stops caused by a statement.

If multi-source replication is used, this statement applies to the default connection. It could be necessary to change the value of the system variable.

Note that, if the event is a , the whole transaction will be skipped. With non-transactional engines, an event is always a single statement.

This statement is valid only when the replica threads are not running. Otherwise, it produces an error.

The statement does not automatically restart the replica threads.

Example

Multi-source replication:

Multiple Replication Domains

sql_slave_skip_counter can't be used to skip transactions on a replica if is in use and if contains multiple values. In that case, you'll get an error like the following:

In order to skip transactions in cases like this, you will have to manually change .

See Also

_{This page is licensed: GPLv2, originally from}