Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: 单节点测试安装3个tikv组件后，强制缩容其中2个tikv，导致tidb启动失败
[TiDB Usage Environment] Testing
[TiDB Version] 6.1.1
[Reproduction Path] After installing 3 TiKV components on a single node for testing, forcibly scale down 2 of the TiKV components, causing TiDB to fail to start.
[Encountered Problem: Symptoms and Impact] According to the TiDB logs, it keeps trying to connect to the 2 TiKV components that have been taken offline.
[Resource Configuration] The test environment configuration is very low.
[Attachments: Screenshots/Logs/Monitoring]
Status of each component:
TiDB component logs:
TiKV component logs:
Is there any way to prevent TiDB from accessing those two TiKV nodes?
It’s normal that it can’t start. With 3 replicas and 3 TiKV nodes, it can only tolerate 1 TiKV failure at most, which is equivalent to losing 2 replicas.
But I only have one node here, is that not possible?
Definitely not, most of the replicas are gone. Refer to this link to try expanding and then repairing.
With multiple replicas in TiKV, if you directly take down 2 out of 3, it definitely won’t work.
I tried the solutions provided by everyone, but none of them worked because my scaling-down operation was too extreme. Since I had previously tested installing a single TiKV component, I thought it would be fine to scale down two of the three TiKV components, but I overlooked the default three-replica setting. I still want to thank everyone for helping me, a novice. Thank you very much. In the end, I reinstalled everything. When I have time, I will review other posts and experiment with those scenarios.
Yes, three nodes are the minimum option.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: Ti青涩
|
username: 
|
username: 
Operations Guide / TiDB Operations Manual - TiDB Q&A Community
|
username: 
|
username: 
|
username: