Machine crash prevents node removal

translator_bot June 23, 2024, 5:25am 1

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

Original topic: 机器宕机没法下节点

| username: xxxxxxxx

TiDB version 4.0.13
Issue: One machine crashed unexpectedly online. Tried to remove the faulty node with --force, but after more than ten minutes, it still couldn’t be removed.

The offline operation is as follows:

The offline operation is stuck at this position and does not time out, which is really frustrating.

translator_bot June 23, 2024, 5:25am 2

| username: xfworld | Original post link

Is it the node that needs to be taken offline that is stuck in pending offline?

translator_bot June 23, 2024, 5:25am 3

| username: wuxiangdong | Original post link

To take TiKV offline, you need to wait for data migration. It’s better to have PD perform some eviction first before taking it offline; this might be better.

translator_bot June 23, 2024, 5:25am 4

| username: alfred | Original post link

What is the current deployment architecture? Can the cluster as a whole still provide services if this node goes down?