A virtual machine node was deleted for some reason, and now it cannot be removed using the scale-down method

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

Original topic: 一个节点的虚拟机因为某些原因被删掉了,现在无法用缩容的方式把这个永久消失的节点删掉。

| username: TiDB_萌新

[TiDB Usage Environment] Testing
[TiDB Version] v7.1.0
[Reproduction Path] Normally deployed on three virtual machines. One of the virtual machines (1kv 1pd) was physically deleted by a colleague.
[Encountered Problem: Problem Phenomenon and Impact]
I want to remove this node by scaling down, but it keeps prompting that the server cannot be found. Shutting down and restarting also prompt that the server cannot be found. Now I just want to ask, under normal circumstances, how should such permanently disappeared nodes be handled?
[Resource Configuration]
[Attachment: Screenshot/Log/Monitoring]

| username: tidb狂热爱好者 | Original post link

No pictures, no configuration details provided.

| username: TiDB_萌新 | Original post link

The configurations are all very standard. They were all successfully deployed. The main issue is that one of the virtual machines was deleted and cannot be restored.

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

I think you might need to try forced scale-in:
tiup cluster scale-in -N --force

However, if you are using 3 replicas by default, forced scale-in might still be pending offline. It is best to first scale out to restore 3 nodes, and then force scale-in the physically deleted node.

| username: srstack | Original post link

tiup cluster scale-in -N --force is a feasible method; force will ignore all error messages, including the inability to link to the corresponding node.

| username: tidb狂热爱好者 | Original post link

To delete, you need to add a node first and then delete the incorrect node. The number of nodes must be >3 to delete.

| username: system | Original post link

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