EC
1983
MySQLWARNINGCriticalReplicationHIGH confidence

Replica ignored table due to replication filter

Production Risk

Medium — ignored tables diverge between source and replica over time.

What this means

A replication event targeting a specific table was skipped on the replica because the table matches a replication filter rule (--replicate-ignore-table, --replicate-wild-ignore-table, etc.).

Why it happens
  1. 1The table is listed in replicate-ignore-table or replicate-wild-ignore-table filter.
  2. 2Statement-based replication event involves a filtered table.
  3. 3Row-based event targets a table excluded by the replica filter.
How to reproduce
trigger — this will error
trigger — this will error
-- On replica with --replicate-ignore-table=mydb.audit_log
-- Source executes: INSERT INTO mydb.audit_log VALUES (...);

expected output

Warning 1983: Slave: ignored table 'mydb.audit_log' due to replication filter.

Fix 1

Review and adjust replication filters if the table should be replicated

Review and adjust replication filters if the table should be replicated
-- Check current filters:
SHOW SLAVE STATUS\G
-- Adjust --replicate-ignore-table in my.cnf and restart

Why this works

Removing the filter will allow the table to replicate normally.

Fix 2

Accept the warning if intentional

Accept the warning if intentional
-- No action needed if filter is intentional

Why this works

Replication filters are a valid way to partially replicate data.

What not to do

✕

Sources
Official documentation ↗

MySQL 8.0 — 1983 ER_SLAVE_IGNORED_TABLE

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

← All MySQL errors