首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >Debezium CDC连接器任务出现错误: javax.management.InstanceAlreadyExistsException

Debezium CDC连接器任务出现错误: javax.management.InstanceAlreadyExistsException
EN

Stack Overflow用户
提问于 2019-07-11 18:50:39
回答 1查看 726关注 0票数 0

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

代码语言:javascript
复制
[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 request用以前的值重新加载了现有的连接器,但没有用。

EN

回答 1

Stack Overflow用户

发布于 2019-07-12 13:49:29

我相信您正在为两个连接器使用相同的database.history.kafka.topic。您应该为每个实例使用unqiue。

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/56987550

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档