@kapa.ai I get this error sometimes when multiple airbyte connection are running in parallel to move data from mysql to gcs : at io.debezium.connector.binlog.BinlogStreamingChangeEventSource.wrap(BinlogStreamingChangeEventSource.java:1206) ... 5 more Caused by: com.github.shyiko.mysql.binlog.network.ServerException: A slave with the same server_uuid/server_id as this slave has connected to the master; the first event '' at 4, the last event read from '/mysql/binlog/mysql-bin.029599' at 2997377, the last byte read from '/mysql/binlog/mysql-bin.029599' at 2997377. at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:1074) ... 3 more 2026-03-14 133201 source ERROR main i.a.c.AirbyteConnectorRunnable(run):38 Failed class io.airbyte.cdk.read.ReadOperation operation execution. org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped. at io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:67) ~[debezium-core-3.1.2.Final.jar:3.1.2.Final] at io.debezium.connector.binlog.BinlogStreamingChangeEventSource$ReaderThreadLifecycleListener.onCommunicationFailure(BinlogStreamingChangeEventSource.java:1252) ~[debezium-connector-binlog-3.1.2.Final.jar:3.1.2.Final] at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:1110) ~[mysql-binlog-connector-java-0.40.2.jar:0.40.2] at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:657) ~[mysql-binlog-connector-java-0.40.2.jar:0.40.2] at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:959) ~[mysql-binlog-connector-java-0.40.2.jar:0.40.2] at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?] Caused by: io.debezium.DebeziumException: A slave with the same server_uuid/server_id as this slave has connected to the master; the first event '' at 4, the last event read from '/mysql/binlog/mysql-bin.029599' at 2997377, the last byte read from '/mysql/binlog/mysql-bin.029599' at 2997377. Error code: 1236; SQLSTATE: HY000. at io.debezium.connector.binlog.BinlogStreamingChangeEventSource.wrap(BinlogStreamingChangeEventSource.java:1206) ~[debezium-connector-binlog-3.1.2.Final.jar:3.1.2.Final] ... 5 more Caused by: com.github.shyiko.mysql.binlog.network.ServerException: A slave with the same server_uuid/server_id as this slave has connected to the master; the first event '' at 4, the last event read from '/mysql/binlog/mysql-bin.029599' at 2997377, the last byte read from '/mysql/binlog/mysql-bin.029599' at 2997377. at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:1074) ~[mysql-binlog-connector-java-0.40.2.jar:0.40.2] ... 3 more Is there a way to fix this ?

Duplicate Server UUID/Server ID Error in MySQL CDC The error you're seeing is:

A slave with the same server_uuid/server_id as this slave has connected to the master

This occurs because when multiple Airbyte CDC connections are running in parallel against the same MySQL source, each Debezium-based connector registers itself as a replication slave. If two or more connections use the same

server_id

, MySQL kicks out the first connection when the second one connects, causing this failure. Unfortunately, the knowledge sources provided do not contain specific documentation or a confirmed fix for this exact

server_uuid/server_id

conflict scenario. The documents in the knowledge base cover related but different MySQL CDC/Debezium errors (binlog deserialization failures, EOFExceptions, etc.). What I can suggest based on general Airbyte MySQL CDC knowledge: The root cause is that each Airbyte MySQL CDC connection needs a unique

server_id

to avoid conflicting with other replication clients. In the Airbyte MySQL source connector configuration, there is typically a "Server ID" field under the CDC settings. You should: 1. Assign a unique

server_id

to each Airbyte connection that reads from the same MySQL instance. Make sure no two connections share the same value, and that the values don't conflict with any existing replication slaves connected to your MySQL master. 2. Check your MySQL source connector settings in Airbyte for each connection and set distinct server IDs (e.g., connection 1 uses

5401

, connection 2 uses

5402

, etc.). > ⚠️ Since this specific fix is not explicitly documented in the provided knowledge sources, I recommend also checking the Airbyte MySQL source documentation and opening a GitHub issue if the problem persists, as the knowledge sources do show an active issue tracker for MySQL CDC problems. [CDC MySQL issue] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.