environment
canal version
canal.deployer-1.1.2
mysql version
5.7.11-enterprise-commercial-advanced-log
Issue Description
我们使用的是mysql企业版,但是遇到的问题是,canal读取到binlog位点之后,会一直卡住不动,kafka里面也没有进入数据,但是当我们使用同样版本的mysql社区版来进行时,不会遇到同样的问题。
canal的日志中会报如下的异常信息,但是之后kafka中会放入一些数据,然后binlog的position就停止一直不动了。
canal.log的异常信息:
com.alibaba.fastsql.sql.parser.ParserException: syntax error, error in :'ord' AS '*E3619321C1A937C46A0D8BD1D, pos 66, line 1, column 64, token AS
at com.alibaba.fastsql.sql.parser.SQLParser.printError(SQLParser.java:363) ~[fastsql-2.0.0_preview_644.jar:2.0.0_preview_644]
at com.alibaba.fastsql.sql.parser.SQLStatementParser.parseStatementList(SQLStatementParser.java:534) ~[fastsql-2.0.0_preview_644.jar:2.0.0_preview_644]
at com.alibaba.fastsql.sql.SQLUtils.parseStatements(SQLUtils.java:525) ~[fastsql-2.0.0_preview_644.jar:2.0.0_preview_644]
at com.alibaba.fastsql.sql.repository.SchemaRepository.console(SchemaRepository.java:439) ~[fastsql-2.0.0_preview_644.jar:2.0.0_preview_644]
at com.alibaba.otter.canal.parse.inbound.mysql.tsdb.MemoryTableMeta.apply(MemoryTableMeta.java:78) ~[canal.parse-1.1.2.jar:na]
at com.alibaba.otter.canal.parse.inbound.mysql.tsdb.DatabaseTableMeta.applyHistoryOnMemory(DatabaseTableMeta.java:463) [canal.parse-1.1.2.jar:na]
at com.alibaba.otter.canal.parse.inbound.mysql.tsdb.DatabaseTableMeta.rollback(DatabaseTableMeta.java:174) [canal.parse-1.1.2.jar:na]
at com.alibaba.otter.canal.parse.inbound.mysql.AbstractMysqlEventParser.processTableMeta(AbstractMysqlEventParser.java:84) [canal.parse-1.1.2.jar:na]
at com.alibaba.otter.canal.parse.inbound.AbstractEventParser$3.run(AbstractEventParser.java:192) [canal.parse-1.1.2.jar:na]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_152]
2019-01-10 09:27:24.901 [destination = example , address = ********:3306 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - ---> find start position successfully, EntryPosition[included=false,journalName=mysql-bin.000085,position=1012563587,serverId=1,gtid=,timestamp=1547082839000] cost : 706839ms , the next step is binlog dump