Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: 扩容的tidb组件启动失败
[TiDB Usage Environment] Production Environment
I followed the official documentation to perform scaling operations. After the scaling was completed, I checked the cluster status and found that the newly scaled TiDB component status was down. After individually starting the node, it was still down upon inspection. Is there any solution for this?
Check the log content of the corresponding tidb-server node.
Please send the TiDB logs for review.
This depends on the logs, as the other TiDB servers are functioning normally.
Is the YAML file format for the scaled-out TiDB node correct?
Check if the newly scaled-out node has been added in the current configuration using tiup cluster edit-config [tidb-test].
First, check the logs of the tidb-server on the down node.
You can also use tiup cluster show-config XXX to see if there is any new node information in the configuration file.
These are the logs from tidb-4000. I don’t know which one to look at, so I sent both.
Try deleting the sock file.
Try starting it manually on the node that is being expanded.
It has been successful, thank you. Why does doing this solve the problem?
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: TiDBer_djgos04V
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: