MySQL connector - CDC - very slow

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu
  • Memory / Disk: VM GCP n2-standard-8 / 50Go Disk size
  • Deployment: Docker
  • Airbyte Version: 0.40.18
  • Source name/version: MySQL version 1.0.21
  • Destination name/version: BigQuery version 1.2.5
  • Step: The issue is happening during sync
  • Description:

Actually i’m trying to ingest data from a MySQL table (CDC) to Bigquery Dataset.
All works well but i have huge ingestion time after the first synchronisation, slower than the first ingestion with fewer data :

As shown on screen for 23 Go synchronisation takes 1h36min but for 6,73Mo it takes 1h54.

Here is my source configuration :

As comparison i have another MySQL source, ingesting data on the same BigQuery destination which take only minutes for bigger volumetry.

The other MySQL source configuration:

Do you have any idea to help me understand this long time ingestion ?

Thanks in advance to your help.

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

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

Hi @marcosmarxm ,

The problem is still existing and actually no solution found.

If someone have any idea or solution please tell me.

Finally i refreshed the connector and it work.
It’s not a production solution but that’s the only one i found.