TiKV status is Tombstone, but unable to clean up using the tiup cluster prune command

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

Original topic: tikv状态为Tombstone,但是使用tiup cluster prune命令无法清理

| username: terry0219

[Test Environment for TiDB] Testing
[TiDB Version] 7.5.0
[Reproduction Path] After simulating the failure of 2 out of 3 TiKV nodes and performing online unsafe recovery, the status changes to Tombstone. Using the tiup cluster prune test-tidb command, the faulty nodes cannot be cleaned.

| username: caiyfc | Original post link

You can take a look at this post.

| username: terry0219 | Original post link

It worked normally after cleaning the meta.yaml file of tiup as mentioned in the documentation, thanks.

| username: caiyfc | Original post link

Ah? I wanted you to handle it according to the best answer and use ctl to delete it. You just changed the topology file, so the nodes are not visible only during display. It’s possible that the information of these two stores is still in PD and hasn’t been deleted.

| username: terry0219 | Original post link

Is it this command: pd-ctl -u <pd_addr> unsafe remove-failed-stores <store_id1,store_id2,...>? This step was already performed in the first step of online unsafe recovery, and it has been confirmed that the store information in the PD nodes has been deleted.

| username: caiyfc | Original post link

If there is no store information in PD, there should be no problem.

| username: dba远航 | Original post link

It’s good that it’s resolved.