EC
1799
MariaDBERRORNotableReplicationHIGH confidence

Binlog logical clock conflict

Production Risk

High — replication halted or inconsistent.

What this means

The binlog logical clock used for parallel replication (LOGICAL_CLOCK dependency tracking) detected a conflict, preventing a transaction from being applied in parallel.

Why it happens
  1. 1Two transactions have conflicting lock dependencies that prevent safe parallel execution under LOGICAL_CLOCK mode.
How to reproduce
trigger — this will error
trigger — this will error
-- Internal error during MTS LOGICAL_CLOCK scheduling; not directly triggerable

expected output

ERROR 1799 (HY000): Logical clock conflict detected during parallel replication.

Fix

Switch slave_parallel_type to DATABASE to avoid LOGICAL_CLOCK conflicts

Switch slave_parallel_type to DATABASE to avoid LOGICAL_CLOCK conflicts
STOP SLAVE;
SET GLOBAL slave_parallel_type = 'DATABASE';
START SLAVE;

Why this works

DATABASE-based parallelism is less aggressive but avoids logical clock conflicts.

What not to do

✕

Version notes

Sources
Official documentation ↗

MySQL 8.0 — 1799 ER_BINLOG_LOGICAL_CLOCK_CONFLICT

Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev

← All MariaDB errors