mysql - Debezium CDC Connector 任务出现错误 : javax. management.InstanceAlreadyExistsException

标签 mysql apache-kafka apache-kafka-connect debezium

我的 debezium mysql 源连接器在 Kafka 上工作。我添加了另一个 debezium mysql 源连接器,使用相同的数据库但数据格式不同。结果,我的第一个连接器开始显示以下错误:

[2019-07-11 10:29:09,125] ERROR WorkerSourceTask{id=debezium-connector-0} Task threw an uncaught and unrecoverable exception 
(org.apache.kafka.connect.runtime.WorkerTask:177)
org.apache.kafka.connect.errors.ConnectException: Encountered change event for table db.user whose schema isn't known to this connector
at io.debezium.connector.mysql.AbstractReader.wrap(AbstractReader.java:230)
at io.debezium.connector.mysql.AbstractReader.failed(AbstractReader.java:208)
at io.debezium.connector.mysql.BinlogReader.handleEvent(BinlogReader.java:508)
at com.github.shyiko.mysql.binlog.BinaryLogClient.notifyEventListeners(BinaryLogClient.java:1095)
at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:943)
at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:580)
at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:825)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.kafka.connect.errors.ConnectException: Encountered change event for table db.user whose schema isn't known to this connector
at io.debezium.connector.mysql.BinlogReader.informAboutUnknownTableIfRequired(BinlogReader.java:758)
at io.debezium.connector.mysql.BinlogReader.handleUpdateTableMetadata(BinlogReader.java:733)
at io.debezium.connector.mysql.BinlogReader.handleEvent(BinlogReader.java:492)
... 5 more
[2019-07-11 10:29:09,125] ERROR WorkerSourceTask{id=debezium- 
connector-krazybee-0} Task is being killed and will not recover 
until manually restarted 
(org.apache.kafka.connect.runtime.WorkerTask:178)
[2019-07-11 10:29:09,125] INFO Stopping MySQL connector task 
(io.debezium.connector.mysql.MySqlConnectorTask:430)
[2019-07-11 10:29:09,125] INFO ChainedReader: Stopping the binlog 
reader (io.debezium.connector.mysql.ChainedReader:121)
[2019-07-11 10:29:09,126] INFO Discarding 0 unsent record(s) due 
to the connector shutting down 
(io.debezium.connector.mysql.BinlogReader:129)
[2019-07-11 10:29:09,126] INFO Discarding 0 unsent record(s) due to the connector shutting down (io.debezium.connector.mysql.BinlogReader:129)

我已使用 REST API 重新启动了 debezium 连接器。

尽管据我所知,debezium 连接器在数据库历史模式中不匹配,但无法弄清楚如何在不删除现有连接器的情况下纠正它。

我还使用 PUT 请求使用以前的值重新加载了现有连接器,但没有用。

最佳答案

我相信您对两个连接器使用相同的database.history.kafka.topic。您应该为每个实例使用唯一的主题。

关于mysql - Debezium CDC Connector 任务出现错误 : javax. management.InstanceAlreadyExistsException,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/56987550/

相关文章:

apache-kafka - Kafka 经纪人间通信

elasticsearch - Kafka连接器Elasticsearch topic.regex

java - 如何使用 Java API 列出 Kafka 集群中所有可用的代理?

sql - 在查询返回的数组中查找某个名称的排名或索引

MySQL查询以查找每月活跃用户

mysql - 如何对具有更多未读消息的用户进行排序,使其首先出现在mysql结果中

docker - 无法将docker app连接到kafka docker容器

apache-spark - 如何为 Kafka Connect 和 Spark 注册和使用 AVRO Schema?

java - Confluence Kafka Streams - 找不到类 io.confluence.connect.avro.ConnectDefault

javascript - 使用 php Onload javascript 不会触发 onload 函数