You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by SA16009066杨飞 <83...@qq.com.INVALID> on 2022/12/02 15:25:48 UTC
kafka connect is unstable

[2022-12-02 22:40:26,771] ERROR WorkerSourceTask{id=mysql-order_middle_prod-dd_ods_otd_helios_lopa_order_middle_prod_1h-connector-0} Task threw an uncaught and unrecoverable exception. Task is being killed and will not recover until manually restarted (org.apache.kafka.connect.runtime.WorkerTask)
org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped.
&nbsp; &nbsp; &nbsp; &nbsp; at io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:50)
&nbsp; &nbsp; &nbsp; &nbsp; at io.debezium.connector.mysql.MySqlStreamingChangeEventSource$ReaderThreadLifecycleListener.onCommunicationFailure(MySqlStreamingChangeEventSource.java:1239)
&nbsp; &nbsp; &nbsp; &nbsp; at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:1079)
&nbsp; &nbsp; &nbsp; &nbsp; at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:631)
&nbsp; &nbsp; &nbsp; &nbsp; at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:932)
&nbsp; &nbsp; &nbsp; &nbsp; at java.lang.Thread.run(Thread.java:748)
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 'mysql-bin.000457' at 364120264, the last event read from 'mysql-bin.000457' at 367556227, the last byte read from 'mysql-bin.000457' at 367556258. Error code: 4052; SQLSTATE: HY000.
&nbsp; &nbsp; &nbsp; &nbsp; at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.wrap(MySqlStreamingChangeEventSource.java:1194)
&nbsp; &nbsp; &nbsp; &nbsp; ... 5 more&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;this seems to be unstable kafka cluester - a worker very likely died, another one with the same ID was started and then the first one was recreated/restarted - with the same ID, leading to a conflict.how to solve this problem