TiDB KV Crash Causes Region is Unavailable

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

Original topic: tidb kv宕机,导致Region is unavailable

| username: Hacker_suny

[TiDB Usage Environment] Production Environment
[TiDB Version] 4.0.11
[Reproduction Path] Physical machine crash
[Encountered Problem: Problem Phenomenon and Impact] Physical machine crash, causing region to be inaccessible. The physical machine cannot be started. I would like to ask if there is any way to synchronize data.
[Resource Configuration]
[Attachment: Screenshot/Log/Monitoring]

| username: TiDBer_pkQ5q1l0 | Original post link

How many machines are down? It seems that one machine doesn’t affect the service usage. You can just scale up by adding one more node.

| username: Hacker_suny | Original post link

One machine went down, but previously it was sharding, not replication. Five machines were used to create three shards.

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

What do you mean, is the number of region replicas set to 1?

| username: 裤衩儿飞上天 | Original post link

Share your topology information and everyone will understand the general idea.

| username: h5n1 | Original post link

| username: system | Original post link

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