1670
MySQLWARNINGNotableReplicationHIGH confidence
Replica silently retried a transaction
Production Risk
Low — retries are normal; persistent retries may indicate a deeper locking issue.
What this means
The replica silently retried a transaction after a temporary failure (e.g., deadlock or lock timeout). This is informational and usually not an error condition.
Why it happens
- 1A transient deadlock or lock wait timeout caused the replica SQL thread to retry the transaction.
- 2slave_transaction_retries is > 0, allowing automatic retries.
How to reproduce
trigger — this will error
trigger — this will error
-- Replica SQL thread encounters a deadlock and retries
expected output
Warning 1670: The slave coordinator and worker threads are stopped, some temporary tables remain open.
Fix
Monitor and tune slave_transaction_retries if retries are frequent
Monitor and tune slave_transaction_retries if retries are frequent
SHOW VARIABLES LIKE 'slave_transaction_retries'; -- Increase if needed: SET GLOBAL slave_transaction_retries = 20;
Why this works
More retries give the replica more attempts to get past transient lock conflicts.
Version notes
Sources
Official documentation ↗
MySQL 8.0 — 1670 ER_SLAVE_SILENT_RETRY_TRANSACTION
Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev