Partially Synced Postgres Connection

Connector Questions & Issues
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu 18.04.4 LTS
  • Memory / Disk: 16GB/ 50GB
  • Deployment: Docker
  • Airbyte Version: 0.40.3
  • Source name/version: Postgres Connector / 1.0.16
  • Destination name/version: Snowflake Destination / 0.4.34
  • Step: The issue is happening during sync

Description
This ticket comes as a continuation to the (Stack Syncs and Automated Full Resyncs on CDC).

For the same described setup:

Connection Info

We have configured one of our connections using postgres-connector and snowflake-destination. From the source database, we have configured 2 tables both in

CDC replication
Incremental & Deduped History
Daily Sync at 9 AM, manually triggered through API (Airflow Operator)
The source database is Aurora Postgres and for the CDC configuration we have followed your setup instructions, which means that we have created

A dedicated read-only user is granted with the relevant privileges
A replication slot using ‘pgoutput’ plugin
A publication slot is registered with the 2 tables.
Furthermore, those 2 configured tables are updated in batch operations, which means that for many days there are zero changes, but then due to a scheduled operation process, thousands of rows are affected (inserts/updates/deletes).

we are facing a new problem, similar with those described in the previous ticket, but different on the behavior and debugging.

After checking the connector on 11/11/2022, we saw that the last sync that brought some changes was on 01/11/2022. After checking both tables we identified that:

  1. Table1 (with the highest volume) was synced correctly since the last change was applied on 31/10/2022.
  2. Table2 (with the lowest volume) was not synced since 18/10/2022. The last update was on 04/11/2022. It is important to state that this table is populated 2-3 times at a maximum every month and the last syncs were:
    2.1 4/11/2022
    2.2 18/10/2022
    2.3 3/10/2022
    2.4 19/9/2022

This means that we are sure that until 31/10/2022 the connection was working correctly. After that date, we lost 1 batch sync for Table2 on 4/11/2022.

From the logs, it’s not clear what is the problem since the syncs are completed successfully. The only thing that we have been identified is that as the days goes by, more and more logs such us

2022-11-11 06:00:45 e[44msourcee[0m > Streaming requested from LSN LSN{FC/D8881A90}, received LSN LSN{FC/D49160F0} identified as already processed
2022-11-11 06:00:45 e[44msourcee[0m > Streaming requested from LSN LSN{FC/D8881A90}, received LSN LSN{0/0} identified as already processed
2022-11-11 06:00:45 e[44msourcee[0m > Streaming requested from LSN LSN{FC/D8881A90}, received LSN LSN{FC/D49168C0} identified as already processed
2022-11-11 06:00:45 e[44msourcee[0m > Streaming requested from LSN LSN{FC/D8881A90}, received LSN LSN{FC/D4916A58} identified as already processed
2022-11-11 06:00:45 e[44msourcee[0m > Streaming requested from LSN LSN{FC/D8881A90}, received LSN LSN{FC/D4916BF0} identified as already processed
2022-11-11 06:00:45 e[44msourcee[0m > Streaming requested from LSN LSN{FC/D8881A90}, received LSN LSN{FC/D4916D88} identified as already processed
2022-11-11 06:00:45 e[44msourcee[0m > Streaming requested from LSN LSN{FC/D8881A90}, received LSN LSN{FC/D4916F28} identified as already processed
2022-11-11 06:00:45 e[44msourcee[0m > Streaming requested from LSN LSN{FC/D8881A90}, received LSN LSN{FC/D49170C8} identified as already processed

are coming, which makes us think that again there may be a problem with identifying the correct LSN pointer to restart the process for each sync.

Logs :
*Some of the relevant 2022-11-11 06:00:45 e[44msourcee[0m > Streaming requested from LSN LSN{FC/D8881A90}, received LSN LSN{FC/D4916BF0} identified as already processed logs have been removed from filed due to >8MB size limitation.`

partial_table_sync__latest_successful_run_table2_19:10:2022.txt.txt (176.9 KB)
partial_table_sync__latest_successful_run_table1_01:11:2022.txt (8.0 MB)
partial_table_sync__latest_problematic_run_11:11:2022.txt (7.6 MB)

partial_table_sync__latest_successful_run_table1_01:11:2022.txt (8.0 MB)
h

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

Hello Giannis Kontogeorgos, it’s been a while without an update from us. Are you still having problems or did you find a solution?