Flink cdc报错问题之使用jdbc connector报错如何解决-阿里云开发者社区

Flink cdc报错问题之使用jdbc connector报错如何解决

2024-02-19 369

版权

本文内容由阿里云实名注册用户自发贡献，版权归原作者所有，阿里云开发者社区不拥有其著作权，亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容，填写侵权投诉表单进行举报，一经查实，本社区将立刻删除涉嫌侵权内容。

本文涉及的产品

实时计算 Flink 版，5000CU*H 3个月

简介： Flink CDC报错指的是使用Apache Flink的Change Data Capture（CDC）组件时遇到的错误和异常；本合集将汇总Flink CDC常见的报错情况，并提供相应的诊断和解决方法，帮助用户快速恢复数据处理任务的正常运行。

问题一：请问大家，flink CDC说是支持clickhouse，但是我使用jdbc connector报错

请问大家，flink CDC说是支持clickhouse，但是我使用jdbc connector报错，在flink官网也没找到clickhouse connector。这是需要自己开发么？

参考答案：

从Flink导入数据至ClickHouse https://help.aliyun.com/document_detail/212262.html

关于本问题的更多回答可点击进行查看：

https://developer.aliyun.com/ask/468603?spm=a2c6h.13066369.question.46.4d426d0c1FNTP6

问题二：在用FlinkCDC的时候有遇到过这个报错吗？

在用FlinkCDC的时候有遇到过这个报错吗？ ERROR io.debezium.connector.mysql.MySqlStreamingChangeEventSource [1268 ] Error during binlog processing. Last offset stored = null, binlog reader near position = mysql-bin.000351/194 FLink> 2023-03-10/18:45:33:589 [blc-rm-2zeh0xq0m99rg0zw0.mysql.rds.aliyuncs.com:3306] ERROR io.debezium.pipeline.ErrorHandler [31 ] Producer failure 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 '/home/mysql/log/mysql/mysql-bin.000351' at 1341674, the last byte read from '/home/mysql/log/mysql/mysql-bin.000351' at 1341674. Error code: 1236; SQLSTATE: HY000. at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.wrap(MySqlStreamingChangeEventSource.java:1383) ~[flink-connector-mysql-cdc-2.3.0.jar:1.6.4.Final] at io.debezium.connector.mysql.MySqlStreamingChangeEventSourceReaderThreadLifecycleListener.onCommunicationFailure(MySqlStreamingChangeEventSource.java:1439)[flink−connector−mysql−cdc−2.3.0.jar:1.6.4.Final]atcom.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:980)[mysql−binlog−connector−java−0.25.3.jar:0.25.3]atcom.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:599)[mysql−binlog−connector−java−0.25.3.jar:0.25.3]atcom.github.shyiko.mysql.binlog.BinaryLogClientReaderThreadLifecycleListener.onCommunicationFailure(MySqlStreamingChangeEventSource.java:1439) [flink-connector-mysql-cdc-2.3.0.jar:1.6.4.Final] at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:980) [mysql-binlog-connector-java-0.25.3.jar:0.25.3] at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:599) [mysql-binlog-connector-java-0.25.3.jar:0.25.3] at com.github.shyiko.mysql.binlog.BinaryLogClient7.run(BinaryLogClient.java:857) [mysql-binlog-connector-java-0.25.3.jar:0.25.3] at java.lang.Thread.run(Thread.java:834) [?:?] 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 '/home/mysql/log/mysql/mysql-bin.000351' at 1341674, the last byte read from '/home/mysql/log/mysql/mysql-bin.000351' at 1341674. at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:944) ~[mysql-binlog-connector-java-0.25.3.jar:0.25.3] ... 3 more