Issue with Incremental Sync in Airbyte

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

Error message ‘Saved offset is before replication slot’s confirmed lsn’ indicates a problem with the initial connection attempting incremental sync instead of full sync replication.


Question

Hi everyone ! I have this following issue when I try to sync some tables for the 1st time, I’m using Incremental | Append + Deduped:
io.airbyte.commons.exceptions.ConfigErrorException: Saved offset is before replication slot's confirmed lsn. Please reset the connection, and then increase WAL retention and/or increase sync frequency to prevent this from happening in the future.
I didn’t find any issues on my PostgreSQL database. I created the replication slot as expected. It looks like the initial connection is attempting to do an incremental sync instead of full sync replication.
Can someone help me, please ?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["incremental-sync", "airbyte-connector", "postgresql", "replication-slot", "full-sync"]
2

Are you on the latest Airbyte and connector versions? I’ve seen some notes related to WAL and first syncs for Postgres and MySQL in the recent releases, so may be worth updating everything first before chasing phantoms that may have already been solved for.

3

Hey Justin, I’m using the cloud version

4

in that case I’d probably recommend putting a ticket in so they can help you work through it. if you end up hearing anything that may be useful to others having this issue though, be sure to post it back here to the community!

5

hi <@U07E9KSQTEX>, please file a ticket and if possible provide the link to the sync that has the issue. We would be happy to take a closer look. If this is the very first, we shall do a full refresh, which shouldn’t trigger this error.