Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: ticdc创建同步任务下游是kafka报错Error: Get “http://127.0.0.1:8300/api/v2/status”: dial tcp 127.0.0.1:8300: connect: connection refused
The image is not visible. Please provide the text you need translated.
Is there an issue with the server information? I see you’re accessing the local port 8300?
Yes, I deployed TiDB locally, and TiCDC is also local.
Try replacing 127 with your IP address.
I have tried it, but it’s the same error.
Check the service with netstat -lntp | grep 8300
.
Check if your port 8300 is up? Use netstat -anp | grep 8300
.
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.
Why can’t this synchronization task be deleted?
Reported this error. My TiDB is version 5.4 and CDC is version 6.5. Will there be a version conflict?
Currently, from the issues visible in the screenshot, 1. There are definitely problems with cross-version compatibility. 2. The method of starting the service might be incorrect. It is recommended to redeploy CDC using TiUP.
Can I upgrade the TiDB cluster version? Should I upgrade to 6 or 6.5?
If it’s a test environment, you can directly upgrade to 6.5.0, and all component versions need to be consistent.
Are there any differences in his startup commands and task synchronization compared to the previous 5.4 version?
How to deal with the issue of no leader shown in the startup command?
After restarting the CDC service, there will be no missing leader, but this error is reported.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.