8000 求解：解析binlog抛出异常 column size is not match for table:user.test_user,30 vs 27 · Issue #1510 · alibaba/canal · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

求解：解析binlog抛出异常 column size is not match for table:user.test_user,30 vs 27 #1510

8000
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
zwh201806 opened this issue Feb 15, 2019 · 6 comments
Closed

求解：解析binlog抛出异常 column size is not match for table:user.test_user,30 vs 27 #1510

zwh201806 opened this issue Feb 15, 2019 · 6 comments

Comments

@zwh201806
Copy link
zwh201806 commented Feb 15, 2019 •
edited
Loading

使用版本 canal.deployer-1.1.3-SNAPSHOT.tar.gz
异常信息：
2019-02-15 10:35:36.342 [destination = test , address = /172.17.139.231:3366 , 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
2019-02-15 10:35:36.343 [destination = test , address = /172.17.139.231:3366 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - prepare to find start position just last position
{"identity":{"slaveId":-1,"sourceAddress":{"address":"172.17.139.231","port":3366}},"postion":{"gtid":"","included":false,"journalName":"mysql-bin.001303","position":523652,"serverId":1877583954,"timestamp":1550138420000}}
2019-02-15 10:35:36.353 [destination =test , address = /172.17.139.231:3366 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - ---> find start position successfully, EntryPosition[included=false,journalName=mysql-bin.001303,position=523652,serverId=1877583954,gtid=,timestamp=1550138420000] cost : 11ms , the next step is binlog dump
2019-02-15 10:35:36.496 [destination = test , address = /172.17.139.231:3366 , EventParser] ERROR c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - dump address 172.17.139.231/172.17.139.231:3366 has an error, retrying. caused by
com.alibaba.otter.canal.parse.exception.CanalParseException: com.alibaba.otter.canal.parse.exception.CanalParseException: parse row data failed.
Caused by: com.alibaba.otter.canal.parse.exception.CanalParseException: parse row data failed.
Caused by: com.alibaba.otter.canal.parse.exception.CanalParseException: column size is not match for table:user.test_user,30 vs 27

biglog部分信息：
image

源码：
image

没搞懂是怎么回事？是否会影响数据同步？
@agapple
Copy link
Member
agapple commented Feb 18, 2019

报错的意思，是指binlog里DML数据的表的列信息 要比 TableMeta里获取到的列信息要多，确认下是否有开启TableMeta TSDB的功能？

@agapple agapple closed this as completed Mar 25, 2019
@godchou
Copy link
godchou commented Oct 24, 2020

canal.instance.tsdb.enable=false 应该设置为false是吧

@qinlz-1
Copy link
qinlz-1 commented Mar 10, 2021

@agapple
开启了TableMeta TSDB 但是还是报这个错
image

@DyzYpp
Copy link
DyzYpp commented Aug 12, 2021

解决了吗

@sugerdudu
Copy link

同问啊

@sugerdudu
Copy link

不管tsdb开启还是关闭，都会报

@quanllong quanllong mentioned this issue Jul 9, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@agapple @sugerdudu @godchou @zwh201806 @DyzYpp @qinlz-1
0