conduktor.io ↗
← All errors
high PostgreSQL MySQL SQL Server MongoDB MariaDB Offset

No previous offset found — starting new snapshot

Root cause

The connector's Kafka Connect offsets topic was deleted, the connector was renamed, or offset data expired. Without an offset, Debezium treats the connector as new and starts from scratch, potentially re-delivering all historical data.

How to fix

  1. Check the offsets topic:
    kafka-console-consumer.sh --bootstrap-server <broker>:9092 --topic connect-offsets --from-beginning --property print.key=true
  2. If offset is lost and data is already downstream, use snapshot.mode=no_data to skip re-reading row data.
  3. To recover schema history (MySQL/MariaDB/SQL Server): set snapshot.mode=recovery.
  4. Protect the offsets topic: set cleanup.policy=compact and retention.ms=-1 so offsets are never lost.
Official Debezium documentation ↗