slave_exec_mode

How replication events should be executed. Legal values are STRICT (default) and IDEMPOTENT. In IDEMPOTENT mode, replication will not stop for operations that are idempotent. For example, in row based replication attempts to delete rows that doesn't exist will be ignored. In STRICT mode, replication will stop on any unexpected difference between the master and the slave.

See also: System Variables in 10.5 ES, in 10.5 CS, in 10.4 ES, in 10.4 CS, in 10.3 ES, in 10.3 CS, in 10.2 ES, and in 10.2 CS

DETAILS

PARAMETERS

Command-line

--slave_exec_mode={STRICT|IDEMPOTENT}

Configuration file

Supported

Dynamic

Yes

Scope

Global

Data Type

ENUM (STRICT, IDEMPOTENT)

Default Value

STRICT

SkySQL Default (Standalone 10.4)

STRICT

SkySQL Default (Standalone 10.5)

STRICT

SkySQL Default (Primary/Replica 10.4)

STRICT

SkySQL Default (Primary/Replica 10.5)

STRICT

SkySQL Default (Analytical 10.4)

STRICT

SkySQL Default (HTAP 10.4)

STRICT

SkySQL Default (Xpand 10.5)

STRICT

See MariaDB SkySQL documentation to learn more about the MariaDB SkySQL database as a service.

CHANGE HISTORY

Release Series

History

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.5 Community

  • Present starting in MariaDB Community Server 10.5.0.

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1.

10.4 Community

  • Present starting in MariaDB Community Server 10.4.0.

10.3 Enterprise

  • Present starting in MariaDB Enterprise Server 10.3.16-1.

10.3 Community

  • Present starting in MariaDB Community Server 10.3.0.

10.2 Enterprise

  • Present starting in MariaDB Enterprise Server 10.2.25-1.

10.2 Community

  • Present starting in MariaDB Community Server 10.2.0.

EXTERNAL REFERENCES