After executing --force to offline a node, PD did not delete the store information

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

Original topic: 执行 --force 下线节点后,pd没有删除store信息

| username: TiDBer_y9Z6xmOI

[TiDB Usage Environment] Production Environment
[TiDB Version] v4.0.14
[Reproduction Path] The machine node went down due to a power outage. After consulting the documentation, I attempted to repair the cluster by first scaling down and then scaling up. Since it was a three-node deployment, I first scaled up by adding one machine, changing the setup to four nodes. Then, I executed the command tiup dm scale-in <cluster-name> --force to forcibly scale down the problematic node.
[Encountered Issue: Symptoms and Impact] After executing the operation, the network recovered, and the scaled-down node could be connected again. However, the store of that node still exists in PD, with used_size=0 and region_count having values that gradually decrease over time but at a slow pace. The tiup cluster display command does not show the status of that node, but it is visible in the dashboard as “scaling down.”
Currently, the data in the tidb-data directory of the scaled-down node has been cleared. I want to restore the cluster to its original state. Could the experts please take a look? Thank you.
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]
image

| username: 我是咖啡哥 | Original post link

Looking at your screenshot, it’s a TiKV node. Why didn’t you use tiup cluster scale-in?

| username: h5n1 | Original post link

Didn’t another post say it has already been restored? When the status changes to up, use the method from the other post. Tiup shows that the meta.yaml file under the .tiup directory should include the scale-in nodes. Or just wait for the region migration to complete and then scale out again.

| username: TiDBer_y9Z6xmOI | Original post link

Yes, the TiKV node was forcibly taken offline.

| username: TiDBer_y9Z6xmOI | Original post link

The command was copied incorrectly, which forced the TiKV node offline.

| username: TiDBer_y9Z6xmOI | Original post link

Can only wait for the offline process to finish?

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

Forced offline, just wait for the offline process to complete. Since we have already expanded the capacity, it shouldn’t affect the business, right?

| username: system | Original post link

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