MySQL source connector: slow CDC replication

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Linux Ami 2
  • Memory / Disk: you can use something like 16Gb / 90 Gb
  • Deployment: Docker
  • Airbyte Version: 0.40.4
  • Source name/version: MySQL 0.6.8
  • Destination name/version: Redshift 0.3.47 (S3 Staging)
  • Step: sync
  • Description: Sync using CDC from MySQL to Redshift is very slow: it takes around 18 mins to sync just 9.9k records or 25 Mb which gives only 550 recs/min speed. See the screenshot. Is there any way to speed it up?

    The logs file is big to be attached here so here is the link to it File Sharing and Transfer - Send Large Files via FEX.NET
    From the logs, it looks like it collects a tiny bit of data and pushes it to the S3 and then repeats.

I’ve been trying to merge 🎉 Destination Redshift: File buffer increase limit by adam-bloom · Pull Request #15707 · airbytehq/airbyte · GitHub to fix this. I’ve been working around this for months by running a custom build of the redshift destination connector that has this fix.

1 Like

Wow, that’s great @adam!
@tuliren could you pls help to merge it or maybe there is an alternative for this issue?

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

@alexnikitchuk glad its only annoying for you :slight_smile: Many of our syncs can include GBs of data that is a bit beyond annoying…it’s untenable…to write to S3 in tiny chunks.

Hopefully that fix is merged soon. We can’t be the only two users who have run into this! I made that change back in June but its taken a while to get through the review process.

Hey I have passed the PR around with the team and have requested to take a look at that in priority. I will also follow up again in the next week. Thanks for your patience.

1 Like

thanks @harshith! Let us know if you need any additional info.