TiKV Abnormal Shutdown and Failure to Restart

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

Original topic: TiKV异常下线 后无法启动

| username: Johnnes_Xnn

[TiDB Usage Environment] Production Environment
[TiDB Version] 7.1.0
[Reproduction Path] Start the abnormally offline TiKV, tiup cluster start tidb-cluster -N ...:20160
[Encountered Problem: TiKV cannot start]
[Resource Configuration]


[Attachments: Screenshots/Logs/Monitoring]

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

Why did you cover all the IPs?

| username: Johnnes_Xnn | Original post link

Isn’t this the production environment IP?

| username: 小龙虾爱大龙虾 | Original post link

Is there production data? If not, forcibly scale down and then scale up again.

| username: dba远航 | Original post link

I feel that there is still too little information to make a judgment.

| username: Johnnes_Xnn | Original post link

What information is needed?

| username: wangccsy | Original post link

Correctly configure the MailBox.

| username: 路在何chu | Original post link

I don’t quite understand the original poster’s meaning. TiKV has already been taken offline, how can it be started?

| username: xingzhenxiang | Original post link

I see the same error here. If it doesn’t work, try scaling down and then scaling up.

| username: Kongdom | Original post link

:joy: At that time, it wasn’t resolved; we just directly scaled up and down.

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

It’s been offline for so long, just scale down and then scale up again…

| username: xingzhenxiang | Original post link

Okay, I thought this was resolved. It’s about scaling in and out. Actually, the best way to solve the issue of a single node being unavailable in a cluster is to scale in and out. It’s a simple and straightforward solution.

| username: system | Original post link

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