Source MSSQL - CDC incremental load failed when there is a batch update at source

  • Is this your first time deploying Airbyte?: No /
  • OS Version / Instance: Ubuntu, Windows or MacOS… are some example remove it with yours
  • Memory / Disk: you can use something like 4Gb / 1 Tb
  • Deployment: Are you using Docker or Kubernetes deployment? k8s
  • Airbyte Version: What version are you using now? 0.40.x
  • Source name/version: source-mssql : 0.4.24
  • Step: The issue is happening during sync, creating the connection or a new source?
  • Description: once in a while there would batch update at source table hence there would huge data needs to be sync and it seems, reading is finished and it failed whilst closing connection but, I have no clue how to mitigate this issue.

“failureOrigin” : “source”,
“internalMessage” : “io.airbyte.workers.general.DefaultReplicationWorker$SourceException: Source cannot be stopped!”,
“externalMessage” : “Something went wrong within the source connector”,
“metadata” : {
“attemptNumber” : 0,
“jobId” : 154332,

c810ba10_3e93_4c4c_976f_8605746e4520_logs_154332_txt.log (2.0 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.
The Community Assistance Team

Thanks for the post @sivankumar86, I saw that you created an issue here: Source Mssql : CDC connector cannot handle large update from source (6GB of data) · Issue #23658 · airbytehq/airbyte · GitHub

The issue has been triaged and added to our team’s backlog, hopefully our team can look into it and figure out what the issue is.

1 Like