Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: tiup cluster reload tidb-cluster 报错
[TiDB Usage Environment] Production Environment
[TiDB Version] 5.2.3
tiup cluster reload tidb-cluster error
Can you manually execute the scp command?
Manual operation doesn’t work either. I changed the port number to 8822.
Then you should first use tiup cluster edit-config tidb-cluster
to modify your SSH port number…

The default is 22, if you don’t change it, it will definitely use 22.
Manually executing the scp
command on the machine also doesn’t work, which indicates that it is unrelated to the TiDB cluster or the tiup tool. The failure of scp
execution means that a normal connection cannot be established. You can check the following items:
- Whether the network from the control machine to the target machine is normal
- Check for network port issues from the control machine to the target machine
- Whether the account from the control machine to the target machine has the necessary permissions
Change back the SSH port for testing. Turn off the firewall on each node. Ensure there are no network issues between the control machine and each machine.
Is the password-free mutual authentication configured correctly without any issues?
You can refer to the previous solutions:
I have already changed it.
I think the main reason is that the default value of the tidb_distsql_scan_concurrency
parameter is 15, which is relatively high. You can try reducing this value to see if it helps.
Is there no problem with the network?
Modify the file name in this directory to solve the problem. It should be an issue with the configuration file loading.
Modify the file name in the directory? From what to what? Which user made the modification? Could it be a file permission issue, such as the user executing tiup not having permission for this file?