Airbyte MariaDB CDC restart failures: inspect the TableMap context behind the offset
A restart offset must identify a decodable event boundary, not merely an increasing number.
Preserve what the offset means
A restart position must allow the required decoding context to be read again. A filename and position supplied to Truthound do not alone establish what can be decoded there. Use approved binlog tooling to identify the required context position independently. [1, 2, 3]
Repeated failures after a successful run
The public Airbyte report reads MariaDB through the MySQL connector, then encounters missing TableMap errors on subsequent CDC startup. The explanation that a saved offset can point inside a statement split into row events is the reporter's hypothesis, not a confirmed code-path analysis. It is not authorization for automatically rewinding offsets. [1]
An illustrative same-file boundary
If an illustrative binlog file requires context beginning at position 100, restarting at 100 satisfies this condition, while 140 misses the earlier context and fails. Positions in different files cannot be compared this way. The actual safe boundary depends on transaction, TableMap and event-skip policies together. [1, 3]
The audit relationship Truthound can inspect
Compare the failing offset, transaction start and TableMap position using approved tooling. After recovery, inspect duplicate replayed keys and deletion effects. Truthound Core's ColumnPairValidator can compare restart and required-context positions within the same file. It does not amend state or recover binlogs. Resume through an operational procedure with preserved state and duplicate handling, then verify business effects separately. [1, 2, 3]
Application conditions
Use approved tooling to establish restart_position, required_context_position, transaction and TableMap locations within the same binlog_file, linking them to recovered keys.
Alternatives
Validate a supported recovery procedure that rereads required context using preserved binlogs and state.
Limitations
Truthound neither arbitrarily rewinds offsets nor recovers binlogs. State changes require preserved copies and an operational duplicate-handling policy.
Evidence
- Event checked
- Subject checked
- Modified
