Help Center> Relational Database Service> Troubleshooting> RDS for MySQL> Primary/Standby Replication Issues> Canal Fails to Parse Binlogs

Updated on 2023-02-07 GMT+08:00

View PDF

Canal Fails to Parse Binlogs

Scenario

An error occurred when Canal parsed binlogs, interrupting binlog collection. The error message is as follows:

xxx.otter.canal.parse.exception.CanalParseException: java.lang.NumberFormatException:- Caused by: java.lang.NumberFormatException:  - at xxx.fastsql.sql.parser.Lexer.integerValue(Lexer.java:2454)

Click to enlarge

Troubleshooting

Check whether the value of binlog_rows_query_log_events of your RDS for MySQL instance is set to 1 or ON.

Canal supports only subscriptions to binlogs in row format.
When the value of binlog_rows_query_log_events is set to 1 or ON, Rows_query events are generated in binlogs. These events are not in row format. In certain scenarios, blank topics may occur in Canal, resulting in a binlog parsing failure.

Solution

Change the value of binlog_rows_query_log_events to OFF and restart the interrupted Canal task.

Parent topic: Primary/Standby Replication Issues

Previous topic: Insufficient Permissions Reported for Canal

Next topic: RDS for MySQL Binlog Issues

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.