Debezium从入门到精通系列之：百篇系列文章汇总之研究Debezium技术遇到的各种错误的解决方法_debezium failed to run embeddedengine

作者：笔触狂放9 | 2024-05-17 13:32:04

踩

debezium failed to run embeddedengine

Debezium从入门到精通系列之：百篇系列文章汇总之研究Debezium技术遇到的各种错误的解决方法

打通Debezium技术的过程中，遇到了一系列的问题，博主会持续总结运用Debezium过程中遇到的错误，现在把各种错误的解决方法汇总到下面的表格中：

未完待续，博主会持续更新Debezium相关的技术文章，大家的支持是我不断创作的动力，欢迎与博主交流Debezium技术，一起加油。

Debezium技术专栏
欢迎私信博主交流数据库和Debezium相关技术，如有需要可以私信加博主微信沟通交流技术

声明：本文内容由网友自发贡献，不代表【wpsshop博客】立场，版权归原作者所有，本站不承担相应法律责任。如您发现有侵权的内容，请联系我们。转载请注明出处：https://www.wpsshop.cn/w/笔触狂放9/article/detail/583802

文章名称	文章链接
Debezium报错处理系列一：The db history topic is missing	Debezium报错处理系列一：The db history topic is missing
Debezium报错处理系列二：Make sure that the same history topic isn‘t shared by multiple connector instances	Debezium报错处理系列二：Make sure that the same history topic isn‘t shared by multiple connector instances
Debezium报错处理系列三：Access denied； you need (at least one of) the SUPER, REPLICATION CLIENT privilege(s)	Debezium报错处理系列三：Access denied； you need (at least one of) the SUPER, REPLICATION CLIENT privilege(s)
Debezium报错处理系列四：Caused by: java.net.SocketException: Connection reset	Debezium报错处理系列四：Caused by: java.net.SocketException: Connection reset
Debezium报错处理系列五：Authentication failed: Invalid username or password	Debezium报错处理系列五：Authentication failed: Invalid username or password
Debezium报错处理系列六：A slave with the same server_uuid/server_id as this slave has connected to the maste	Debezium报错处理系列六：A slave with the same server_uuid/server_id as this slave has connected to the maste
debezium报错处理系列七：The database history couldn’t be recovered. Consider to increase the value for database.	debezium报错处理系列七：The database history couldn’t be recovered. Consider to increase the value for database.
debezium报错处理系列八：DDL statement couldn‘t be parsed.	debezium报错处理系列八：DDL statement couldn‘t be parsed.
debezium报错处理系列九：“ddl“ : “# Dummy event replacing event type 160 that slave cannot handle.“	debezium报错处理系列九：“ddl“ : “# Dummy event replacing event type 160 that slave cannot handle.“
Debezium报错处理系列十：Could not find existing binlog information while attempting schema only recovery snashot	Debezium报错处理系列十：Could not find existing binlog information while attempting schema only recovery snashot
Debezium报错处理系列十一：Data row is smaller than a column index, internal schema representation is probably out of sync with real database schema	Debezium报错处理系列十一：Data row is smaller than a column index, internal schema representation is probably out of sync with real database schema
Debezium报错处理系列十二：Cannot enlarge string buffer containing 1073740820 bytes by 1704 more bytes.	Debezium报错处理系列十二：Cannot enlarge string buffer containing 1073740820 bytes by 1704 more bytes.
Debezium报错处理系列十三：Caused by: java.io.EOFException	Debezium报错处理系列十三：Caused by: java.io.EOFException
Debezium报错处理系列十四： Invalid Java object for schema type INT64: class java.lang.String for field: “null	Debezium报错处理系列十四： Invalid Java object for schema type INT64: class java.lang.String for field: “null
debezium报错处理系列之十五：no longer available on the server. Reconfigure the connector to use a snapshot when neede	debezium报错处理系列之十五：no longer available on the server. Reconfigure the connector to use a snapshot when neede
Debezium报错处理系列之十六：Caused by: java.io.EOFException: Failed to read remaining 7 of 23 bytes from	Debezium报错处理系列之十六：Caused by: java.io.EOFException: Failed to read remaining 7 of 23 bytes from
Debezium报错处理系列之十七：Caused by: javax.management.InstanceAlreadyExistsException	Debezium报错处理系列之十七：Caused by: javax.management.InstanceAlreadyExistsException
Debezium报错处理系列之十八：解决无法获取表结构问题	Debezium报错处理系列之十八：解决无法获取表结构问题
Debezium报错处理系列之十九：The replication sender thread cannot start in AUTO_POSITION mode	Debezium报错处理系列之十九：The replication sender thread cannot start in AUTO_POSITION mode
Debezium报错处理系列之二十：task failed to create new topic.Ensure that the task is authorized to create topics	Debezium报错处理系列之二十：task failed to create new topic.Ensure that the task is authorized to create topics
Debezium报错处理系列之二十一： Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server	Debezium报错处理系列之二十一： Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server
Debezium报错处理系列之二十二：SchemaBuilderException: Cannot create field because of field name duplication	Debezium报错处理系列之二十二：SchemaBuilderException: Cannot create field because of field name duplication
Debezium报错处理系列之二十三：Caused by: java.lang.IndexOutOfBoundsException: No group 2	Debezium报错处理系列之二十三：Caused by: java.lang.IndexOutOfBoundsException: No group 2
Debezium报错处理系列之二十四：Caused by: org.postgresql.util.PSQLException: ERROR: replication slot \“debezium\“	Debezium报错处理系列之二十四：Caused by: org.postgresql.util.PSQLException: ERROR: replication slot \“debezium\“
Debezium报错处理系列之二十五：Client requested master to start replication from impossible position	Debezium报错处理系列之二十五：Client requested master to start replication from impossible position
Debezium报错处理系列之二十六：Caused by: io.debezium.DebeziumException: Failed to read next byte from position	Debezium报错处理系列之二十六：Caused by: io.debezium.DebeziumException: Failed to read next byte from position
Debezium报错处理系列之二十七：io.debezium.DebeziumException: Failed to deserialize data of EventHeaderV4	Debezium报错处理系列之二十七：io.debezium.DebeziumException: Failed to deserialize data of EventHeaderV4
Debezium报错处理系列之二十八： Expiring 1 record(s) for test-ts-0:120001 ms has passed since batch creation	Debezium报错处理系列之二十八： Expiring 1 record(s) for test-ts-0:120001 ms has passed since batch creation
Debezium报错处理系列之二十九：Make sure that an instance of SQL Server is running on the host and accepting TCP	Debezium报错处理系列之二十九：Make sure that an instance of SQL Server is running on the host and accepting TCP
Debezium报错处理系列之三十：SQLServerException: 服务器主体 \“dwCDC\“ 无法在当前安全上下文下访问数据库 \“dw\“。	Debezium报错处理系列之三十：SQLServerException: 服务器主体 \“dwCDC\“ 无法在当前安全上下文下访问数据库 \“dw\“。
Debezium报错处理系列之三十一：Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: 为过程或函数 cdc.fn_cdc	Debezium报错处理系列之三十一：Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: 为过程或函数 cdc.fn_cdc
Debezium报错处理系列之三十二：Unable to connect: Public Key Retrieval is not]	Debezium报错处理系列之三十二：Unable to connect: Public Key Retrieval is not
Debezium报错处理系列之三十三：Unexpected error while connecting to MySQL and looking at BINLOG_FORMAT	Debezium报错处理系列之三十三：Unexpected error while connecting to MySQL and looking at BINLOG_FORMAT
Debezium报错处理系列之三十四：io.debezium.DebeziumException: The db history topic or its content is fully or partially missing. Please check database history topic configuration and re-execute the snapshot	Debezium报错处理系列之三十四：io.debezium.DebeziumException: The db history topic or its content is fully or partially missing. Please check database history topic configuration and re-execute the snapshot
Debezium报错处理系列之三十五：ERROR WorkerSourceTask{id=mysql-nus_chat_prod-dd_ods_nus_chat_prod_1h-connector-0} Failed to flush, timed out while waiting for producer to flush outstanding 195 messages (org.apache.kafka.connect.runtime.WorkerSourceTask)	Debezium报错处理系列之三十五：ERROR WorkerSourceTask{id=mysql-nus_chat_prod-dd_ods_nus_chat_prod_1h-connector-0} Failed to flush, timed out while waiting for producer to flush outstanding 195 messages (org.apache.kafka.connect.runtime.WorkerSourceTask)
Debezium报错处理系列之三十六：Task threw an uncaught and unrecoverable exception. Task is being killed and will not recover until manually restarted	Debezium报错处理系列之三十六：Task threw an uncaught and unrecoverable exception. Task is being killed and will not recover until manually restarted
Debezium报错处理系列之三十七：Error configuring an instance of KafkaSchemaHistory；	Debezium报错处理系列之三十七：Error configuring an instance of KafkaSchemaHistory；
Debezium报错处理系列之三十八：Timeout expired while fetching topic metadata	Debezium报错处理系列之三十八：Timeout expired while fetching topic metadata
Debezium报错处理系列之三十九：Debezium Server实际应用报错No resolvable bootstrap urls given in bootstrap.servers	Debezium报错处理系列之三十九：Debezium Server实际应用报错No resolvable bootstrap urls given in bootstrap.servers
Debezium报错处理系列之四十：Debezium Server实际应用报错“message“:“JAAS config entry not terminated by semi-colon“	Debezium报错处理系列之四十：Debezium Server实际应用报错“message“:“JAAS config entry not terminated by semi-colon“