TiDB Table Region is Unavailable Exception: Unable to Delete Table

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

Original topic: tidb表 Region is unavailable 异常 表删除不掉

| username: Hacker_UBVfs1Zv

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]


Unable to drop the table, how to forcefully delete the table.

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

There must be an issue with the cluster, otherwise, how could the table not be deleted?

| username: Hacker_UBVfs1Zv | Original post link

The cluster is scaling down.

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

Uh, it might be that the region was moving when you checked. Try looking again later.

| username: Hacker_UBVfs1Zv | Original post link

Shrinking caused regions to be lost quickly, and the table cannot be deleted. How to handle this? How to force delete the table? It still cannot be deleted now.

| username: h5n1 | Original post link

What are the steps for scaling down? Describe the specific symptoms of region loss. Please post the status of tiup cluster display.

| username: WalterWj | Original post link

Scaling down will not cause region loss.

Normal scaling down requires waiting for data to be completed before stopping the scaling down node. Has the current data been completed? Do not perform any operations on the scaling down node yet…

| username: 田帅萌7 | Original post link

ADMIN SHOW DDL JOBS take a look

| username: Hacker_UBVfs1Zv | Original post link

Forced a scale-down operation midway through by executing a force command.

| username: Hacker_UBVfs1Zv | Original post link

Can’t execute it.

| username: Hacker_UBVfs1Zv | Original post link

I deleted all the jobs but it still doesn’t work.

| username: miya | Original post link

It could be caused by region migration. You can check if it meets the TiDB data routing rules or if there is any data transformation.

| username: 像风一样的男子 | Original post link

List all your operation steps, how many KVs there are in total, how many were compacted, and when the compaction was forced.

| username: 源de爸 | Original post link

Take a look at the system logs.

| username: TIDB-Learner | Original post link

Be patient and wait for the result of the last execution. Some of the next steps cannot be rushed.