Error while processing event at offset

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu
  • Deployment: Kubernetes
  • Airbyte Version: What version are you using now?
  • Source name/version: 0.40.6
  • Destination name/version: Postgres 1.10
  • Step: Sync
  • Description:

When syncing a table in incremental / append, I got the following error

Stack Trace: org.apache.kafka.connect.errors.ConnectException: Error while processing event at offset {transaction_id=null, lsn_proc=12926205003784, lsn_commit=12926205004408, lsn=12926205003784, txId=473266806, ts_usec=1664860439939306}

After the error airbyte retries and starts syncing the table from the beginning, successfully this time. The thing is we collect the table entirely every day.

Do you have an idea on the root cause ?

I attach the log

Thanks :slight_smile:
failing_log.txt (6.1 MB)

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

Could you try a newer connector version and see if the issue persists? We are at 1.0.13 now and there have been some pretty big changes: https://docs.airbyte.com/integrations/sources/postgres#changelog

I do see some parsing errors in the logs around the timestamp that are causing the offset error pasted in this ticket, if the issue doesn’t go away then I will reproduce it.

2022-10-03 05:38:52 e[44msourcee[0m > Cannot parse column default value 'CURRENT_TIMESTAMP' to type 'timestamp'. Expression evaluation is not supported. 2022-10-03 05:38:52 e[44msourcee[0m > Cannot parse column default value 'CURRENT_TIMESTAMP' to type 'timestamp'. Expression evaluation is not supported.
2022-10-03 05:38:53 e[44msourcee[0m > Cannot parse column default value 'CURRENT_TIMESTAMP' to type 'timestamp'. Expression evaluation is not supported. 2022-10-03 05:38:53 e[44msourcee[0m > Cannot parse column default value 'CURRENT_TIMESTAMP' to type 'timestamp'. Expression evaluation is not supported.
2022-10-03 05:38:53 e[44msourcee[0m > Stopping the embedded engine
2022-10-03 05:38:53 e[44msourcee[0m > Waiting for PT5M for connector to stop
2022-10-03 05:43:47 e[44msourcee[0m > Stopping the task and engine
2022-10-03 05:43:47 e[44msourcee[0m > Stopping down connector
2022-10-03 05:45:17 e[44msourcee[0m > Coordinator didn't stop in the expected time, shutting down executor now
2022-10-03 05:45:17 e[44msourcee[0m > Producer failure

Hi @sh4sh

Even with the last version (PG 1.0.14) I still have the same issue sadly :confused:

The last thing I can try is to reset the stream but I would lose all my historical data

Seems related to a lack of resources of our source database

Thanks for the update! Yeah, I was not able to reproduce it so far. Were you able to improve the behaviour?