Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: tikv报错连接20160端口超时
[Test Environment for TiDB] Testing
[TiDB Version] v5.2.0
[Reproduction Path] Restart the cluster
[Encountered Issue: Phenomenon and Impact] Timeout when connecting to tikv port 20160. Error: failed to start tikv: failed to start: 192.168.2.128 tikv-20160.service, please check the instance’s log(/data1/tidb-deploy/tikv-20160/log) for more detail.: timed out waiting for port 20160 to be started after 10m0s
[Resource Configuration] 16C32G*2
[Attachments: Screenshots/Logs/Monitoring]
Check if the port is occupied:
netstat -nltp | grep 20160
Checked, it is not occupied.
Take a look at the contents of the tikv.log on this TiKV. Is the firewall on this TiKV turned off?
If the TiKV directory is deleted and there are no log files, can I recreate the directory and restart the cluster to generate logs?
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.
What does deleting the directory mean? Was it deleted after it couldn’t start or before it couldn’t start? This TiKV is already useless and needs to be scaled in to reduce capacity.
It’s already fixed. Just run the startup script once and it will work.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: TiDBer_x0JaEBMZ
|
username: 
|
username: 
|
username: 
|
username: