简体繁体 English

由于错误代码 1236，无法启动 debezium MySQL 连接器

[英]Cannot start debezium MySQL connector due to Error code 1236

原文 2021-04-19 17:43:37 8 1 mysql/ apache-kafka/ apache-kafka-connect/ debezium

When I check the status of my debezium connector via the kakfa-connect's REST API, I see this error message for the connector:当我通过 kakfa-connect 的 REST API 检查我的 debezium 连接器的状态时，我看到连接器的以下错误消息：

org.apache.kafka.connect.errors.ConnectException: The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. org.apache.kafka.connect.errors.ConnectException：从站正在使用 CHANGE MASTER TO MASTER_AUTO_POSITION = 1 进行连接，但主站已清除包含从站需要的 GTID 的二进制日志。 Error code: 1236;错误代码：1236； SQLSTATE: HY000.\n\tat io.debezium.connector.mysql.AbstractReader.wrap(AbstractReader.java:230)\n\tat io.debezium.connector.mysql.AbstractReader.failed(AbstractReader.java:197)\n\tat io.debezium.connector.mysql.BinlogReader$ReaderThreadLifecycleListener.onCommunicationFailure(BinlogReader.java:997)\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:950)\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:580)\n\t SQLSTATE: HY000.\n\tat io.debezium.connector.mysql.AbstractReader.wrap(AbstractReader.java:230)\n\tat io.debezium.connector.mysql.AbstractReader.failed(AbstractReader.java:197)\n \tat io.debezium.connector.mysql.BinlogReader$ReaderThreadLifecycleListener.onCommunicationFailure(BinlogReader.java:997)\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:950)\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:580)\n\t at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:825)\n\tat java.lang.Thread.run(Thread.java:748)\nCaused by: com.github.shyiko.mysql.binlog.network.ServerException: The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:914)\n\t... 3 more\n at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:825)\n\tat java.lang.Thread.run(Thread.java:748)\nCaused by: com.github.shyiko. mysql.binlog.network.ServerException: The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient. listenForEventPackets(BinaryLogClient.java:914)\n\t... 3 更多\n

Is this an issue with how I am configuring my debezium connector or an issue with MySQL?这是我如何配置我的 debezium 连接器的问题还是 MySQL 的问题？ Whats crazy is that even when I tried setting the option snapshot.mode to never and this error is still being thrown, According to the documentation, when snapshot.mode is set to either never or when_needed it should not require the GTID so I am super confused as to what is happening疯狂的是，即使我尝试将选项snapshot.mode设置为never并且仍然抛出此错误，根据文档，当snapshot.mode设置为never或when_needed它不应该需要 GTID 所以我超级对正在发生的事情感到困惑

1 个解决方案

The problem is that Debezium was probably down for some time and some of the transactions it has not seen are no longer available on the server.问题是 Debezium 可能已经关闭了一段时间，并且它没有看到的一些事务在服务器上不再可用。