开发者社区> 问答> 正文

日志格式问题

instance 看到不同的格式类型 ,其中一种日志格式如果出现报错根本看不出 (就是下面的第一种格式类型的日志,看不出报错原因)

第一种日志格式类型:

2021-10-13 16:23:12.798 [MultiStageCoprocessor-Parser-yxy_platform_order_instance-1] WARN c.a.o.canal.parse.inbound.mysql.dbsync.LogEventConvert - table parser error : header { version: 1 logfileName: "mysql-bin.000443" logfileOffset: 629440910 serverId: 1469116791 serverenCode: "UTF-8" executeTime: 1634113392000 sourceType: MYSQL schemaName: "yxy_weixin" tableName: "qywx_external_user_followers" eventLength: 419 eventType: UPDATE props { key: "rowsCount" value: "1" } } entryType: ROWDATA storeValue: "" storeValue: tableId: 330 eventType: UPDATE isDdl: false rowDatas { beforeColumns { index: 0 sqlType: 12 updated: false isNull: false …………

第二种日志格式类型

2021-10-13 16:21:32.102 [destination = yxy_usercenter_instance , address = dz_mysql_yxy_usercenter_s1.alihbc.local/172.22.10.32:3306 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - ---> begin to find start position, it will be long time for reset or first position 2021-10-13 16:21:32.104 [destination = yxy_usercenter_instance , address = dz_mysql_yxy_usercenter_s1.alihbc.local/172.22.10.32:3306 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - prepare to find start position just last position {"identity":{"slaveId":-1,"sourceAddress":{"address":"dz_mysql_yxy_usercenter_s1.alihbc.local","port":3306}},"postion":{"gtid":"","included":false,"journalName":"mysql-bin.000078","position":789000180,"serverId":1015667897,"timestamp":1634113283000}} 2021-10-13 16:21:32.108 [destination = yxy_usercenter_instance , address = dz_mysql_yxy_usercenter_s1.alihbc.local/172.22.10.32:3306 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - ---> find start position successfully, EntryPosition[included=false,journalName=mysql-bin.000078,position=789000180,serverId=1015667897,gtid=,timestamp=1634113283000] cost : 6ms , the next step is binlog dump

原提问者GitHub用户qinlz-1

展开
收起
山海行 2023-04-27 15:42:07 98 0
1 条回答
写回答
取消 提交回答
  • table parser error的意思就是binlog里的列和tablemeta里的列信息不匹配

    原回答者GitHub用户agapple

    2023-04-27 21:49:45
    赞同 展开评论 打赏
问答排行榜
最热
最新

相关电子书

更多
PostgresChina2018_赖思超_PostgreSQL10_hash索引的WAL日志修改版final 立即下载
Kubernetes下日志实时采集、存储与计算实践 立即下载
日志数据采集与分析对接 立即下载