From ad8bb096c1166650bb03a9b8ad38a0aa763bda40 Mon Sep 17 00:00:00 2001
From: Joyinqin <joyinqin@pku.edu.cn>
Date: Tue, 29 Jun 2021 09:53:20 +0800
Subject: [PATCH] Update scale-tidb-using-tiup.md

---
 scale-tidb-using-tiup.md | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/scale-tidb-using-tiup.md b/scale-tidb-using-tiup.md
index 87752f7d467cc..761de3d818d28 100644
--- a/scale-tidb-using-tiup.md
+++ b/scale-tidb-using-tiup.md
@@ -391,16 +391,6 @@ In special cases (such as when a node needs to be forcibly taken down), or if th
         
 3. Wait for the store of the TiFlash node to disappear or for the `state_name` to become `Tombstone` before you stop the TiFlash process.
 
-    If, after waiting for a long time, the node still fails to disappear or the `state_name` fails to become `Tombstone`, consider using the following command to force the node out of the cluster.
-
-    **Note that the command will directly discard the replicas on the TiFlash node, which might cause the query to fail.**
-
-    {{< copyable "shell-regular" >}}
-
-    ```shell
-    curl -X POST 'http://<pd-address>/pd/api/v1/store/<store_id>/state?state=Tombstone'
-    ```
-
 4. Manually delete TiFlash data files (whose location can be found in the `data_dir` directory under the TiFlash configuration of the cluster topology file).
 
 5. Manually update TiUP's cluster configuration file (delete the information of the TiFlash node that goes down in edit mode).