Summary
User is experiencing intermittent connection failures with MySQL source in Airbyte, receiving a non-zero exit code error. Seeking advice on preventing future sync failures.
Question
Hi everyone! 
I’m currently working with many MySQL sources (MySQL v3.7.3) set to run on a schedule every 10 minutes. Occasionally, I encounter an issue where Airbyte can’t connect to the source. Here’s the error message I receive:
• *Source process exited with non-zero exit code 143*
• *Failure in source:* Checking source connection failed - please review this connection’s configuration to prevent future syncs from failing.
MySQL seems to be running stably without restarts. Does anyone have advice on how to avoid this issue?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
['mysql', 'connection-issue', 'airbyte', 'error-code-143']
replication-orchestrator > failures: [ {
“failureOrigin” : “source”,
“failureType” : “system_error”,
“internalMessage” : “io.airbyte.cdk.integrations.source.relationaldb.state.FailedRecordIteratorException: java.lang.RuntimeException: java.lang.RuntimeException: io.debezium.DebeziumException: Error reading MySQL variables: Communications link failure\n\nThe last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.”,
“externalMessage” : “Something went wrong in the connector. See the logs for more details.”,
It depends how often is “occasionally”.
I’d check number of connections to MySQL and CPU/memory metrics of MySQL server. I’d increase number of retries before failing https://docs.airbyte.com/operator-guides/configuring-airbyte#jobs
Sometimes, you cannot get rid of all the “hiccups” in the infrastructure.
It depends how often is "occasionally". - actually in average 5-6 times per days (schedule every 10 minutes)
I already checked config number of connections/timestamps limit etc in MySQL.
will try to increase MAX_FAILED_JOBS_IN_A_ROW_BEFORE_CONNECTION_DISABLE to 3
thanks for ur advise)
replication-orchestrator > failures: [ {
“failureOrigin” : “source”,
“failureType” : “system_error”,
“internalMessage” : “io.airbyte.cdk.integrations.source.relationaldb.state.FailedRecordIteratorException: java.lang.RuntimeException: java.lang.RuntimeException: io.debezium.DebeziumException: Error reading MySQL variables: Communications link failure\n\nThe last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.”,
“externalMessage” : “Something went wrong in the connector. See the logs for more details.”,
It depends how often is “occasionally”.
I’d check number of connections to MySQL and CPU/memory metrics of MySQL server. I’d increase number of retries before failing https://docs.airbyte.com/operator-guides/configuring-airbyte#jobs
Sometimes, you cannot get rid of all the “hiccups” in the infrastructure.
It depends how often is "occasionally". - actually in average 5-6 times per days (schedule every 10 minutes)
I already checked config number of connections/timestamps limit etc in MySQL.
will try to increase MAX_FAILED_JOBS_IN_A_ROW_BEFORE_CONNECTION_DISABLE to 3
thanks for ur advise)