Debezium for MySQL解析binlog报错

最新推荐文章于 2024-08-21 23:04:05 发布
最新推荐文章于 2024-08-21 23:04:05 发布
阅读量5.8k 收藏 1
点赞数
分类专栏： 大数据 kafka
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/lzufeng/article/details/81488524
版权

运行在Kafka Connect 分布式worker上的debezium for mysql connector报错：

{"name":"debezium-mysql-source-dev","connector":{"state":"RUNNING","worker_id":"192.168.1.200:18083"},"tasks":[{"state":"FAILED","trace":"org.apache.kafka.connect.errors.ConnectException: Unexpected exception while parsing statement /* ApplicationName=IntelliJ IDEA 2017.2.4 */ ALTER TABLE fund_account ALTER COLUMN is_use_pay SET DEFAULT 0 at line 1, column 99
    at io.debezium.connector.mysql.AbstractReader.wrap(AbstractReader.java:200)
    at io.debezium.connector.mysql.AbstractReader.failed(AbstractReader.java:178)
    at io.debezium.connector.mysql.BinlogReader.handleEvent(BinlogReader.java:452)
    at com.github.shyiko.mysql.binlog.BinaryLogClient.notifyEventListeners(BinaryLogClient.java:1055)
    at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:913)
    at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:559)
    at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:793)
    at java.lang.Thread.run(Thread.java:748)
Caused by: io.debezium.text.ParsingException: Unexpected exception while parsing statement /* ApplicationName=IntelliJ IDEA 2017.2.4 */ ALTER TABLE fund_account ALTER COLUMN is_use_pay SET DEFAULT 0 at line 1, column 99
    at io.debezium.relational.ddl.LegacyDdlParser.parsingFailed(LegacyDdlParser.java:555)
    at io.debezium.relational.ddl.LegacyDdlParser.parse(LegacyDdlParser.java:227)
    at io.debezium.relational.ddl.LegacyDdlParser.parse(LegacyDdlParser.java:200)
    at io.debezium.connector.mysql.MySqlSchema.applyDdl(MySqlSchema.java:297)
    at io.debezium.connector.mysql.BinlogReader.handleQueryEvent(BinlogReader.java:637)
    at io.debezium.connector.mysql.BinlogReader.handleEvent(BinlogReader.java:436)
    ... 5 more
Caused by: java.lang.NullPointerException
    at io.debezium.connector.mysql.MySqlDdlParser.parseAlterSpecification(MySqlDdlParser.java:1296)
    at io.debezium.connector.mysql.MySqlDdlParser.parseAlterSpecificationList(MySqlDdlParser.java:1254)
    at io.debezium.connector.mysql.MySqlDdlParser.parseAlterTable(MySqlDdlParser.java:1237)
    at io.debezium.connector.mysql.MySqlDdlParser.parseAlter(MySqlDdlParser.java:1199)
    at io.debezium.connector.mysql.MySqlDdlParser.parseNextStatement(MySqlDdlParser.java:177)
    at io.debezium.relational.ddl.LegacyDdlParser.parse(LegacyDdlParser.java:219)
    ... 9 more
","id":0,"worker_id":"192.168.1.100:18083"}],"type":"source"}

看了一下connector的配置内容：

{
 "name":"debezium-mysql-source-dev",
 "config":{
    "connector.class": "io.debezium.connector.mysql.MySqlConnector",
    "database.hostname": "192.168.1.204",
    "database.port": "3306",
    "database.user": "***",
    "database.password": "****",
    "database.server.id": "184054",
    "database.server.name": "dev",
    "table.whitelist":"simu_ann_dev.announcement_member,simu_ann_dev.announcement_follower,simu_affair_dev.affair_member,simu_affair_dev.role",
    "database.history.kafka.bootstrap.servers": "192.168.1.204:9092,192.168.1.100:9092,192.168.1.200:9092",
    "database.history.kafka.topic": "schema-changes.dev" ,
    "include.schema.changes": "true" ,
    "mode":"incrementing",
    "snapshot.mode":"schema_only_recovery",
    "incrementing.column.name":"id"
  }
}

一开始尝试把”include.schema.changes”配置成false，发现还是不行。

查看connctor运行的task所在的worker节点的connectDistributed.out中的更详细的报错信息：

INFO: Connected to 192.168.1.204:3306 at mysql-bin.000098/467648 (sid:184054, cid:59755)
[2018-08-07 19:05:15,309] INFO Connected to MySQL binlog at 192.168.1.204:3306, starting at binlog file 'mysql-bin.000098', pos=467648, skipping 2 events plus 0 rows (io.debezium.connector.mysql.BinlogReader:941)
[2018-08-07 19:05:15,309] INFO WorkerSourceTask{id=debezium-mysql-source-dev-0} Source task finished initialization and start (org.apache.kafka.connect.runtime.WorkerSourceTask:165)
[2018-08-07 19:05:15,311] INFO Creating thread debezium-mysqlconnector-dev-binlog-client (io.debezium.util.Threads:247)
[2018-08-07 19:05:15,364] INFO Cluster ID: rse1l3gPRJW9-aJLJMB8YA (org.apache.kafka.clients.Metadata:265)
[2018-08-07 19:05:15,370] ERROR Error during binlog processing. Last offset stored = null, binlog reader near position = mysql-bin.000098/467713 (io.debezium.connector.mysql.BinlogReader:967)
[2018-08-07 19:05:15,371] ERROR Failed due to error: Error processing binlog event (io.debezium.connector.mysql.BinlogReader:179)
org.apache.kafka.connect.errors.ConnectException: Unexpected exception while parsing statement /* ApplicationName=IntelliJ IDEA 2017.2.4 */ ALTER TABLE fund_account ALTER COLUMN is_use_pay SET DEFAULT 0 at line 1, column 99
        at io.debezium.connector.mysql.AbstractReader.wrap(AbstractReader.java:200)
        at io.debezium.connector.mysql.AbstractReader.failed(AbstractReader.java:178)
        at io.debezium.connector.mysql.BinlogReader.handleEvent(BinlogReader.java:452)
        at com.github.shyiko.mysql.binlog.BinaryLogClient.notifyEventListeners(BinaryLogClient.java:1055)
        at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:913)
        at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:559)
        at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:793)
        at java.lang.Thread.run(Thread.java:748)
Caused by: io.debezium.text.ParsingException: Unexpected exception while parsing statement /* ApplicationName=IntelliJ IDEA 2017.2.4 */ ALTER TABLE fund_account ALTER COLUMN is_use_pay SET DEFAULT 0 at line 1, column 99
        at io.debezium.relational.ddl.LegacyDdlParser.parsingFailed(LegacyDdlParser.java:555)
        at io.debezium.relational.ddl.LegacyDdlParser.parse(LegacyDdlParser.java:227)
        at io.debezium.relational.ddl.LegacyDdlParser.parse(LegacyDdlParser.java:200)
        at io.debezium.connector.mysql.MySqlSchema.applyDdl(MySqlSchema.java:298)
        at io.debezium.connector.mysql.BinlogReader.handleQueryEvent(BinlogReader.java:637)
        at io.debezium.connector.mysql.BinlogReader.handleEvent(BinlogReader.java:436)
        ... 5 more
Caused by: java.lang.NullPointerException
        at io.debezium.connector.mysql.MySqlDdlParser.parseAlterSpecification(MySqlDdlParser.java:1296)
        at io.debezium.connector.mysql.MySqlDdlParser.parseAlterSpecificationList(MySqlDdlParser.java:1254)
        at io.debezium.connector.mysql.MySqlDdlParser.parseAlterTable(MySqlDdlParser.java:1237)
        at io.debezium.connector.mysql.MySqlDdlParser.parseAlter(MySqlDdlParser.java:1199)
        at io.debezium.connector.mysql.MySqlDdlParser.parseNextStatement(MySqlDdlParser.java:177)
        at io.debezium.relational.ddl.LegacyDdlParser.parse(LegacyDdlParser.java:219)
        ... 9 more
[2018-08-07 19:05:15,373] INFO Error processing binlog event, and propagating to Kafka Connect so it stops this connector. Future binlog events read before connector is shutdown will be ignored. (io.debezium.connector.mysql.BinlogReader:457)

从中看到了binlog日志的文件，去mysql的binlog日志文件（日志在mysql的/etc/my.cnf中配置的binlog文件位置）中查看信息。

root@ubuntu-204:/var/log/mysql# mysqlbinlog  --no-defaults --start-position=467648  --stop-position 469713 ./mysql-bin.000098
/*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/;
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
# at 4
#180806  6:40:30 server id 1  end_log_pos 123 CRC32 0x2da62c9f  Start: binlog v 4, server v 5.7.21-log created 180806  6:40:30
BINLOG '
3nxnWw8BAAAAdwAAAHsAAAAAAAQANS43LjIxLWxvZwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXwAEGggAAAAICAgCAAAACgoKKioAEjQA
AZ8spi0=
'/*!*/;
# at 467648
#180806 12:16:35 server id 1  end_log_pos 467713 CRC32 0x9678a828   Anonymous_GTID  last_committed=832  sequence_number=833 rbr_only=no
SET @@SESSION.GTID_NEXT= 'ANONYMOUS'/*!*/;
# at 467713
#180806 12:16:35 server id 1  end_log_pos 467906 CRC32 0x193b98c0   Query   thread_id=55848 exec_time=0 error_code=0
use `menkor_dev`/*!*/;
SET TIMESTAMP=1533528995/*!*/;
SET @@session.pseudo_thread_id=55848/*!*/;
SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=0, @@session.unique_checks=1, @@session.autocommit=1/*!*/;
SET @@session.sql_mode=1436549152/*!*/;
SET @@session.auto_increment_increment=1, @@session.auto_increment_offset=1/*!*/;
/*!\C utf8mb4 *//*!*/;
SET @@session.character_set_client=45,@@session.collation_connection=45,@@session.collation_server=224/*!*/;
SET @@session.lc_time_names=0/*!*/;
SET @@session.collation_database=DEFAULT/*!*/;
/* ApplicationName=IntelliJ IDEA 2017.2.4 */ ALTER TABLE fund_account ALTER COLUMN is_use_pay SET DEFAULT 0
/*!*/;
# at 467906
#180806 12:26:09 server id 1  end_log_pos 467971 CRC32 0x28ebc3fa   Anonymous_GTID  last_committed=833  sequence_number=834 rbr_only=yes
/*!50718 SET TRANSACTION ISOLATION LEVEL READ COMMITTED*//*!*/;
SET @@SESSION.GTID_NEXT= 'ANONYMOUS'/*!*/;
# at 467971
#180806 12:26:09 server id 1  end_log_pos 468059 CRC32 0xf281f0a1   Query   thread_id=55839 exec_time=0 error_code=0
SET TIMESTAMP=1533529569/*!*/;
/*!\C utf8mb4 *//*!*/;
SET @@session.character_set_client=224,@@session.collation_connection=224,@@session.collation_server=224/*!*/;
....

可以看到报错的行内容是”/* ApplicationName=IntelliJ IDEA 2017.2.4 */ ALTER TABLE fund_account ALTER COLUMN is_use_pay SET DEFAULT 0”。

然而到现在还是没找到线索。查看了报错所在的源码：

    protected void parseAlterSpecification(Marker start, TableEditor table, Consumer<TableId> newTableName) {
        parseTableOptions(start, table);
        if (tokens.canConsume("ADD")) {
            if (tokens.matches("COLUMN", "(") || tokens.matches('(')) {
                tokens.canConsume("COLUMN");
                parseCreateDefinitionList(start, table);
            } else if (tokens.canConsume("PARTITION", "(")) {
                parsePartitionDefinition(start, table);
                tokens.consume(')');
            } else {
                parseCreateDefinition(start, table, true);
            }
        } else if (tokens.canConsume("DROP")) {
            if (tokens.canConsume("PRIMARY", "KEY")) {
                table.setPrimaryKeyNames();
            } else if (tokens.canConsume("FOREIGN", "KEY")) {
                tokens.consume(); // foreign key symbol
            } else if (tokens.canConsumeAnyOf("INDEX", "KEY")) {
                tokens.consume(); // index name
            } else if (tokens.canConsume("PARTITION")) {
                parsePartitionNames(start);
            } else {
                if(!isNextTokenQuotedIdentifier()) {
                    tokens.canConsume("COLUMN");
                }
                String columnName = parseColumnName();
                table.removeColumn(columnName);
                tokens.canConsume("RESTRICT");
            }
        } else if (tokens.canConsume("ALTER")) {
            if (!isNextTokenQuotedIdentifier()) {
                tokens.canConsume("COLUMN");
            }
            String columnName = tokens.consume(); // column name
            if (!tokens.canConsume("DROP", "DEFAULT")) {
                tokens.consume("SET");
                //就是下面这行报空指针异常的
                ColumnEditor columnEditor = table.columnWithName(columnName).edit();
                parseDefaultClause(start, columnEditor);
            }
        } else if (tokens.canConsume("CHANGE")) {
            if (!isNextTokenQuotedIdentifier()) {
                tokens.canConsume("COLUMN");
            }
            String oldName = parseColumnName();
            String newName = parseColumnName();
            parseCreateColumn(start, table, oldName, newName);
        } else if (tokens.canConsume("MODIFY")) {
            if (!isNextTokenQuotedIdentifier()) {
                tokens.canConsume("COLUMN");
            }
            String columnName = parseColumnName();
            parseCreateColumn(start, table, columnName, null);
        } else if (tokens.canConsumeAnyOf("ALGORITHM", "LOCK")) {
            tokens.canConsume('=');
            tokens.consume();
        } else if (tokens.canConsume("DISABLE", "KEYS")
                || tokens.canConsume("ENABLE", "KEYS")) {} else if (tokens.canConsume("RENAME", "INDEX")
                        || tokens.canConsume("RENAME", "KEY")) {
            tokens.consume(); // old
            tokens.consume("TO");
            tokens.consume(); // new
        } else if (tokens.canConsume("RENAME")) {
            tokens.canConsumeAnyOf("AS", "TO");
            TableId newTableId = parseQualifiedTableName(start);
            newTableName.accept(newTableId);
        } else if (tokens.canConsume("ORDER", "BY")) {
            consumeCommaSeparatedValueList(start); // this should not affect the order of the columns in the table
        } else if (tokens.canConsume("CONVERT", "TO", "CHARACTER", "SET")
                || tokens.canConsume("CONVERT", "TO", "CHARSET")) {
            tokens.consume(); // charset name
            if (tokens.canConsume("COLLATE")) {
                tokens.consume(); // collation name
            }
        } else if (tokens.canConsume("CHARACTER", "SET")
                || tokens.canConsume("CHARSET")
                || tokens.canConsume("DEFAULT", "CHARACTER", "SET")
                || tokens.canConsume("DEFAULT", "CHARSET")) {
            tokens.canConsume('=');
            String charsetName = tokens.consume(); // charset name
            table.setDefaultCharsetName(charsetName);
            if (tokens.canConsume("COLLATE")) {
                tokens.canConsume('=');
                tokens.consume(); // collation name (ignored)
            }
        } else if (tokens.canConsume("DISCARD", "TABLESPACE") || tokens.canConsume("IMPORT", "TABLESPACE")) {
            // nothing
        } else if (tokens.canConsume("FORCE")) {
            // nothing
        } else if (tokens.canConsume("WITH", "VALIDATION") || tokens.canConsume("WITHOUT", "VALIDATION")) {
            // nothing
        } else if (tokens.canConsume("DISCARD", "PARTITION") || tokens.canConsume("IMPORT", "PARTITION")) {
            if (!tokens.canConsume("ALL")) {
                tokens.consume(); // partition name
            }
            tokens.consume("TABLESPACE");
        } else if (tokens.canConsume("COALLESCE", "PARTITION")) {
            tokens.consume(); // number
        } else if (tokens.canConsume("REORGANIZE", "PARTITION")) {
            parsePartitionNames(start);
            tokens.consume("INTO", "(");
            do {
                parsePartitionDefinition(start, table);
            } while (tokens.canConsume(','));
            tokens.consume(')');
        } else if (tokens.canConsume("EXCHANGE", "PARTITION")) {
            tokens.consume(); // partition name
            tokens.consume("WITH", "TABLE");
            parseSchemaQualifiedName(start); // table name
            if (tokens.canConsumeAnyOf("WITH", "WITHOUT")) {
                tokens.consume("VALIDATION");
            }
        } else if (tokens.matches(TokenStream.ANY_VALUE, "PARTITION")) {
            tokens.consumeAnyOf("TRUNCATE", "CHECK", "ANALYZE", "OPTIMIZE", "REBUILD", "REPAIR");
            tokens.consume("PARTITION");
            if (!tokens.canConsume("ALL")) {
                parsePartitionNames(start);
            }
        } else if (tokens.canConsume("REMOVE", "PARTITIONING")) {
            // nothing
        } else if (tokens.canConsume("UPGRADE", "PARTITIONING")) {
            // nothing
        }
    }

笔者在源码位置加了点日志：

                logger.info("列名="+columnName);
                Column column = table.columnWithName(columnName);
                logger.info("列信息="+column);
                ColumnEditor columnEditor = column.edit();

然后根据源码构建jar报，上传到kafka connect的插件目录中，再一次执行debezium for mysq connector，发现如下日志：

[2018-08-07 20:40:10,287] INFO 列名=is_use_pay (io.debezium.connector.mysql.MySqlDdlParser:1296)
[2018-08-07 20:40:10,288] INFO 列信息=null (io.debezium.connector.mysql.MySqlDdlParser:1298)

看来是列信息为null导致的空指针。具体什么原因导致的，还不知道。

笔者最近事情比较多，仔细回看日志后发现，导致报错的binlog是笔者table.whitelist之外的表，很奇怪，不监控的表的binlog日志解析报错竟然会影响到整个connector。好在笔者的业务需求不需要知道表的结构变化，所以改了一下connector的配置，暂时解决了问题：

{
 "name":"debezium-mysql-source-dev",
 "config":{
    "connector.class": "io.debezium.connector.mysql.MySqlConnector",
    "database.hostname": "192.168.1.204",
    "database.port": "3306",
    "database.user": "*****",
    "database.password": "*****",
    "database.server.id": "184054",
    "database.server.name": "dev",
    "table.whitelist":"simu_ann_dev.announcement_member,simu_ann_dev.announcement_follower,simu_affair_dev.affair_member,simu_affair_dev.role",
    "database.history.kafka.bootstrap.servers": "192.168.1.204:9092,192.168.1.100:9092,192.168.1.200:9092",
    "database.history.kafka.topic": "schema-changes.dev" ,
    "include.schema.changes": "true" ,
    "mode":"incrementing",
    "incrementing.column.name":"id",
    "database.history.store.only.monitored.tables.ddl":"true",
    "database.history.skip.unparseable.ddl":"true"
  }
}

等不忙的时候得好好把debezium研究一下。

pilaf1990
关注
专栏目录
【Flink】Error during binlog processing last offset stored = null binglog reader near position
九师兄
11-07 2244
1.概述 flink 读取mysql binglog的时候报错如下 Error during binlog processing last offset stored = null binglog reader near position 对应的代码如下 引入如下 原因如下 [呲牙] mysql binlog 日志被提前删除了？感觉像是找不到需要的 binlog 日志呢 查看log如下 这里可以看 估计是过期太快，这里可以设置 读取失败 应该是这个原因 https://stackoverf
Debezium报错处理系列之第103篇：Error processing binlog event whose schema isn‘t known to this connector
zhengzaifeidelushang的博客
06-18 105
Debezium从入门到精通系列之：研究Debezium技术遇到的各种错误解决方法汇总： 更多Debezium技术请参考博主Debezium技术专栏：org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped. at io.debezium.pipeline.ErrorHandler.setProduce
【FLINKCDC】运行时经常server-id冲突报错？一招实现自动化！
smallbag66666的博客
08-21 748
FlinkCDC自动化server-id配置
Debezium指定binlog位置初始化异常排查修复
yyoc97的专栏
05-17 3522
文章目录异常现象如何复现排查定位线索定位 异常现象 最近项目需要使用Debezium指定binlog位置读取数据，当配置FileDatabaseHistory 保存offset就会出现无法识别schema异常。 14:52:18.237 [blc-9.135.12.10:3307] ERROR io.debezium.connector.mysql.MySqlStreamingChangeEventSource - Encountered change event 'Event{header=EventHe
Debezium报错处理系列之第113篇：Cannot read the binlog filename and position via ‘SHOW MASTER STATUS‘.
zhengzaifeidelushang的博客
07-09 250
Debezium报错处理系列之第113篇：Cannot read the binlog filename and position via 'SHOW MASTER STATUS'. Make sure your server is correctly configured
mysql Binlog Reader_聊聊debezium的BinlogReader
weixin_28811227的博客
02-01 492
序本文主要研究一下debezium的BinlogReaderReaderdebezium-v1.1.1.Final/debezium-connector-mysql/src/main/java/io/debezium/connector/mysql/Reader.javapublic interface Reader {public static enum State {/*** The read...
kafka connector mysql_debezium、kafka connector 解析 mysql binlog 到 kafak
weixin_39830303的博客
01-20 291
目的： 需要搭建一个可以自动监听MySQL数据库的变化，将变化的数据捕获处理，此处只讲解如何自动捕获mysql 中数据的变化使用的技术一、思路需要一台 Centos 7.x 的虚拟机 ，zk、debezium、kafka、confluent 运行在 虚拟机上 ，mysql 运行在 windows 系统上，虚拟机监听 window 环境下的 mysql 数据变化二、MySQL 环境准备首先需要找到 ...
Debezium报错处理系列之第109篇：解决升级日志解析jar包重启集群出现的字段类型和值不匹配的错误
zhengzaifeidelushang的博客
07-05 109
Debezium从入门到精通系列之：研究Debezium技术遇到的各种错误解决方法汇总：更多Debezium技术请参考博主Debezium技术专栏：错误1：13MySqlValueConvertersjava304atiodebeziumrelationalTableSchemaBuilderlambda5TableSchemaBuilderjava280。
监听mysql bin文件,使用Binlog+FlinkCDC实时监控数据
weixin_42514521的博客
03-27 4565
一、MySql的Binlog1、什么是Binlog1)binlog是二进制日志，并且是事务安全性2)binlog记录了所有的DDL和DML(除了数据查询语句)语句，并以事件的形式记录,还包含语句所执行的消耗的时间3)一般来说开启二进制日志大概会有1%的性能损耗。2、Binlog使用场景1)使用binlog恢复数据2)在项目中动态监听mysql中变化的数据3、Binlog开启1)在MySQL的配置文...
基于Kafka Debezium Confluent实现MySql实时同步到ES
zj007ok的专栏
04-27 1923
实现目标 基于MySql的Binlog实现Mysql表实时同步到ES。 实现方案 1、总体技术方案基于Kafka的Connect技术。具体技术内容，不做介绍，网上有相关文章，本文章主要解决如何配置，因为网上大部分配置都是只能简单运行，只能插入，不能实现数据按照主键进行更新和删除同步的。 2、基于debezium的MySqlConnecto...
Debezium报错处理系列之四十三：Debezium Server实际应用报错“message“:“Could not find a ‘KafkaClient‘ entry in the JAAS
zhengzaifeidelushang的博客
02-11 417
Debezium报错处理系列之四十三：Debezium Server应用报错"message":"Could not find a 'KafkaClient' entry in the JAAS
实时采集报错：io.debezium.DebeziumException: Unknown command Error code: 1047； SQLSTATE: HY000.
wlove514的博客
01-10 1252
使用KafkaConnect对MySQL进行实时采集的过程中出现启动异常的问题，其中集群环境和MySQL服务器均在云服务。
Debezium报错处理系列之第110篇： ERROR Error during binlog processing.Access denied
zhengzaifeidelushang的博客
07-05 249
Debezium报错处理系列之第110篇：ERROR Error during binlog processing. Last offset stored = null, binlog reader near position = /4 Access denied; you need at least one of the REPLICATION SLAVE privilege for this operation
使用mysql-binlog-connector-java监听mysql的binlog
Fuly的博客
08-19 901
mysql监听的binlog
出现Caused by: java.lang.NullPointerException异常的解决方法
你误入了一条咸鱼的博客
03-21 5804
出现Caused by: java.lang.NullPointerException异常的解决方法
MySql实时数据变更事件捕获kafka confluent之debezium
weixin_34342578的博客
08-21 1772
official Debezium，demo github.com/moxingwang/… 本文主要讲在kafka confluent的基础上如何使用debezium插件获取mysql binlog数据事件完成实时数据流，debezium是以插件的方式配合confluent使用。 如果你的后端应用数据存储使用的MySQL，项目中如果有这样的业务场景你会怎么做呢？ 分库分表数据拆分和迁移...
解决mysql8.0主从配置，从库连接报错：Authentication plugin ‘caching_sha2_password‘ reported error
qun7559的博客
02-26 9637
解决mysql8.0主从配置，从库连接报错：Authentication plugin 'caching_sha2_password' reported error
记mysql版本问题踩的坑
qq_38319289的博客
08-11 506
我的mysql的版本为：8.0.16 JDK版本为：13 报错时用的mysql connector包的版本为：mysql-connector-java-5.1.36-bin 一开始查看对应版本感觉没问题！！这是最坑的！ 官网的版本对应如下： 我寻思着5.1的兼容我的jdk和mysql版本的呀！然后我就找其他的错误！然鹅，他喵的就是版本问题的错误。最后实在找不出其他错误，更改成了mysql-connector-java-5.1.49-bin（这时候已经绝望了，死马当活马医的心态）。然鹅还有错误： 报错Tue
Debezium NPE 的 bug
cainiao1412的博客
10-20 705
最终通过追踪源码，定位到是一个简单的null值判断，修复后，问题解决。
mysql 解析binlog命令
最新发布
09-07
MySQL的二进制日志（Binary Log）是一个用于记录所有对数据库更改的操作的日志文件，这对于数据恢复和主从复制至关重要。解析binlog命令主要是通过mysqlbinlog工具来完成的，它允许用户查看、重放或提取数据库的事务信息。 使用`mysqlbinlog`命令的基本语法如下： ```bash mysqlbinlog [选项] < binlog-file-position | server-id > output-file ``` - `binlog-file-position`：指定二进制日志文件的位置，可以是文件名加上偏移量，或者是基于时间戳的位置。 - `server-id`：如果多个服务器共享同一个二进制日志文件，需要提供对应的server_id来区分来自哪个服务器的事件。 - `output-file`：指定输出重放操作到的文件或标准输出。 一些常用的选项包括： - `-v` 或 `--verbose`：增加输出的详细程度。 - `-t` 或 `--timestamp`：仅显示事件的时间戳。 - `-r` 或 `--rotate`：每条日志结束时重定向输出到新的文件。
评论 3
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值