TiDB Node Fails to Start

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tidb 节点无法启动

| username: 小鱼吃大鱼

TiDB node cannot start

| username: TI表弟 | Original post link

Has there been an upgrade? It looks like the versions are not quite consistent. Is TiKV 6.2.0?

| username: TI表弟 | Original post link

It looks like it’s due to the version.

| username: TiDB_C罗 | Original post link

Insufficient resources, perhaps.

| username: 小鱼吃大鱼 | Original post link

Indeed, the physical files of TiKV were copied from version 4.0.4.

| username: Jellybean | Original post link

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:

  • Check if the PD node is down or if the network is functioning properly.
  • Verify that the PD address in the TiDB configuration file is correct.
  • Check the firewall settings in the TiDB cluster to ensure that the PD node’s port can be accessed.
  • Check the clock synchronization settings in the TiDB cluster to ensure that the clocks of all nodes are synchronized properly.

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.

| username: TI表弟 | Original post link

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?

| username: 小鱼吃大鱼 | Original post link

Deployed on a single server, the PD node is normal.

| username: Jellybean | Original post link

The version issue also needs to be addressed first.

| username: dba远航 | Original post link

It feels like it was caused by a parameter configuration error.

| username: 有猫万事足 | Original post link

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.

| username: 小鱼吃大鱼 | Original post link

The CPU is fine, single-node deployment is possible.

| username: TI表弟 | Original post link

It feels like increasing complexity. If there’s a problem in a certain version, handle it in that version.

| username: 小龙虾爱大龙虾 | Original post link

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?

| username: TI表弟 | Original post link

His data version does not match the TiKV version.

| username: 小鱼吃大鱼 | Original post link

I will restore it once on the original version.

| username: TI表弟 | Original post link

It is recommended to restore the data on version 4.0.4 and then upgrade.

| username: TI表弟 | Original post link

Yes, replying with good data, it seems that upgrading to this version is the only way to do it.

| username: 像风一样的男子 | Original post link

You can refer to this for region repair:

| username: TI表弟 | Original post link

Impressive, impressive.