Snowflake connection cancelling middle of reading records. Sync worker failed

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Windows
  • Memory / Disk: you can use something like 16Gb / 256Gb
  • Deployment: Docker
  • Airbyte Version: 0.39.42-alpha
  • Source name/version: MongoDb (0.1.15)
  • Destination name/version: Snowflake (0.4.34)
  • Step: The issue is happening during sync.
  • Description:

The issue I ran into is I believe my snowflake connection is dropping mid process or not connecting properly. I’ve ran test on the connection, via settings, on both the source and destination and they were successful. I’m not too sure what might be the issue, I see that there’s a DEADLINE_EXCEEDED in the logs and it seems that it was midway of reading records for a replication task the destination cancelled. When I check the activity of on snowflake it seems to be creating and dropping AIRBYTE_CONNECTION_TEST stages. If it matters, I am using OpenVPN because our mongoDB requires a VPN connection to access.

Here are the logs.
logs-27 (2).txt (230.2 KB)

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.
The Community Assistance Team

Hey @raymond_chow, I see your Airbyte version is quite behind - would you be able to update it? Same goes for the connectors. That could be causing some of the issues, so I’d like to eliminate that possibility first.