Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: tidb 节点无法启动

TiDB node cannot start
Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: tidb 节点无法启动
TiDB node cannot start
Has there been an upgrade? It looks like the versions are not quite consistent. Is TiKV 6.2.0?
Indeed, the physical files of TiKV were copied from version 4.0.4.
The error “tikv 9001” indicates that TiDB cannot connect to PD, which may be due to a PD node failure or network issues.
To resolve this issue, you can try the following solutions:
Additionally, the version in the last line of the image seems to have an issue. It shows 6.2.0-alpha, which is different from the version displayed above. Make sure that the same version of components is used within the same cluster, otherwise, strange issues may occur.
Let’s talk about the background. It seems like it could be a version issue or a resource issue. How can we prove which component’s version is the problem?
It feels like it was caused by a parameter configuration error.
Is the CPU sufficient? Sometimes when there are many components deployed on a single machine, PD might not get enough runtime, which can also cause this error.
It feels like increasing complexity. If there’s a problem in a certain version, handle it in that version.
The version 6.2.0 mentioned upstairs, the log indicates the minimum TiKV version, right? I understand that this would normally appear during startup, and it has nothing to do with this, right?
It is recommended to restore the data on version 4.0.4 and then upgrade.
Yes, replying with good data, it seems that upgrading to this version is the only way to do it.