一、报错日志
Caused by: io.debezium.DebeziumException: org.apache.flink.util.FlinkRuntimeException: Cannot read the binlog filename and position via 'SHOW MASTER STATUS'. Make sure your server is correctly configured
at org.apache.flink.cdc.connectors.mysql.debezium.task.MySqlSnapshotSplitReadTask.execute(MySqlSnapshotSplitReadTask.java:134) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at org.apache.flink.cdc.connectors.mysql.debezium.reader.SnapshotSplitReader.snapshot(SnapshotSplitReader.java:176) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at org.apache.flink.cdc.connectors.mysql.debezium.reader.SnapshotSplitReader.lambda$submitSplit$1(SnapshotSplitReader.java:161) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_412]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_412]
... 1 more
Caused by: org.apache.flink.util.FlinkRuntimeException: Cannot read the binlog filename and position via 'SHOW MASTER STATUS'. Make sure your server is correctly configured
at org.apache.flink.cdc.connectors.mysql.debezium.DebeziumUtils.currentBinlogOffset(DebeziumUtils.java:143) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at org.apache.flink.cdc.connectors.mysql.debezium.task.MySqlSnapshotSplitReadTask.doExecute(MySqlSnapshotSplitReadTask.java:156) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at org.apache.flink.cdc.connectors.mysql.debezium.task.MySqlSnapshotSplitReadTask.execute(MySqlSnapshotSplitReadTask.java:129) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at org.apache.flink.cdc.connectors.mysql.debezium.reader.SnapshotSplitReader.snapshot(SnapshotSplitReader.java:176) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at org.apache.flink.cdc.connectors.mysql.debezium.reader.SnapshotSplitReader.lambda$submitSplit$1(SnapshotSplitReader.java:161) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_412]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_412]
... 1 more
Caused by: java.sql.SQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'MASTER STATUS' at line 1
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120) ~[mysql-connector-java-8.0.22.jar:8.0.22]
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97) ~[mysql-connector-java-8.0.22.jar:8.0.22]
at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) ~[mysql-connector-java-8.0.22.jar:8.0.22]
at com.mysql.cj.jdbc.StatementImpl.executeQuery(StatementImpl.java:1200) ~[mysql-connector-java-8.0.22.jar:8.0.22]
at io.debezium.jdbc.JdbcConnection.queryAndMap(JdbcConnection.java:641) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at io.debezium.jdbc.JdbcConnection.queryAndMap(JdbcConnection.java:510) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at org.apache.flink.cdc.connectors.mysql.debezium.DebeziumUtils.currentBinlogOffset(DebeziumUtils.java:123) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at org.apache.flink.cdc.connectors.mysql.debezium.task.MySqlSnapshotSplitReadTask.doExecute(MySqlSnapshotSplitReadTask.java:156) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at org.apache.flink.cdc.connectors.mysql.debezium.task.MySqlSnapshotSplitReadTask.execute(MySqlSnapshotSplitReadTask.java:129) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at org.apache.flink.cdc.connectors.mysql.debezium.reader.SnapshotSplitReader.snapshot(SnapshotSplitReader.java:176) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at org.apache.flink.cdc.connectors.mysql.debezium.reader.SnapshotSplitReader.lambda$submitSplit$1(SnapshotSplitReader.java:161) ~[blob_p-916429e34e7e81044b5e0a15a59b94423de0f995-2d2f6d334847d4017dc084f29d5f56fb:3.3.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_412]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_412]
... 1 more
二、原因
8.0.x binlog 查询点位支持 show master status;
https://dev.mysql.com/doc/refman/8.0/en/change-master-to.html
8.4.x binlog 查询点位不支持 show master status; 改为 SHOW BINARY LOG STATUS;
https://dev.mysql.com/doc/refman/8.4/en/show-master-status.html
三、解决方案
- 换 mysql 版本。
- 修改 FLINK CDC 源码。
