Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: 配置TiCDC报错版本不兼容
【TiDB Usage Environment】POC
【TiDB Version】v5.2.1
【Encountered Issue】After deploying version 5.2.1 using tiup and configuring the cdc component in topology.yaml, the cdc status shows as up and normal. However, when creating a cdc task, the cdc component automatically upgrades to 6.2.0 and then reports an error that the cluster version is too low and needs to be upgraded to 6.2.0.
【Reproduction Path】Install TiDB version 5.2.1 using tiup, and add the cdc component in topology.yaml.
【Issue Phenomenon and Impact】
【Attachments】
Grafana monitoring:
- TiUP Cluster Display information
- TiUP Cluster Edit config information
- TiDB-Overview monitoring
- Corresponding module Grafana monitoring (if any, such as BR, TiDB-binlog, TiCDC, etc.)
- Corresponding module logs (including logs one hour before and after the issue)
Your cluster and CDC nodes are both normal, but the changefeed was not successfully created, right? Can you show the command you used to create the changefeed and the error message? I suspect that the ctl version you used to create the changefeed is not 5.2.1.
Hello, please execute ./cdc version
in the cdc bin directory and provide the result.
Also, please post the specific error logs, thank you~
I think the problem is that the tidb-server
process is not running. You can check the status of the tidb-server
process using the ps
command. If it is not running, you can start it using the systemctl start tidb
command.
The default value of tidb_enable_clustered_index
is INT_ONLY
, which means that only tables with integer primary keys will use clustered indexes by default. If you want to enable clustered indexes for all tables, you need to set this parameter to ON
.
Hello, the root cause of the error is that you used the v6.2.0 cdc ctl to control the v5.2.1 cluster. You just need to specify the version like this: tiup cdc:v5.2.1 cli
.
The CLI in version 6.2.0 is no longer compatible with lower versions of the CDC server.
Based on your suggestion, the issue has been resolved. Thank you very much.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.