After forcing the TiFlash node offline, the status of TiFlash remains Offline

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

Original topic: tiflash节点强制下线后tiflash的状态一直为Offline

| username: haoshuaili

[TiDB Usage Environment] Production Environment
[TiDB Version] v4.0.8
After forcibly taking the TiFlash node offline, the TiFlash status remains Offline.


Currently, the TiFlash node is shut down and does not exist. In this state, what method should I use to remove the abnormal TiFlash node? Is it possible to forcibly change the TiFlash node status from Offline to Tombstone?

| username: tidb菜鸟一只 | Original post link

Offline means it is going offline, and it will become Tombstone after a while, right?

| username: srstack | Original post link

tiup cluster prune --force

| username: WalterWj | Original post link

If you are using TiFlash, this version is outdated, it is recommended to upgrade.

| username: haoshuaili | Original post link

I have already used tiup to force offline. Now the status is offline and it seems there is no way to convert it to Tombstone.

| username: WalterWj | Original post link

How many TiFlash nodes do you have, and how many replicas are configured for the table?

| username: haoshuaili | Original post link

In fact, TiFlash has already been completely decommissioned, and the machines are no longer there. However, its status on PD is still offline. Now we just want to clean up the dirty data.

| username: h5n1 | Original post link

  1. The table needs to set the tiflash replica to 0.
  2. Manually add the scheduling.
| username: haoshuaili | Original post link

The issue has been resolved. I forced the offline status to tombstone and then cleared the tombstone nodes to restore normal operation. However, this method seems to be no longer applicable in versions 5.x and above.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.