Error "Region is unavailable" during DM load phase

Translated
1

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

Original topic: DM load阶段报错Region is unavailable

| username: TiDBer_hwEZA4rV

Originally, there were no issues with full database synchronization plus incremental synchronization. Later, due to some data issues, the entire database was dropped and then re-synchronized in full, resulting in this error. I’m not sure how to resolve it effectively?

2
| username: Billmay表妹 | Original post link

What version~

What actions did you take~

3
| username: TiDBer_hwEZA4rV | Original post link

Cluster version: v5.4.2
Operation:
Deleted the database and resynchronized it from the upstream MySQL using DM in full + incremental mode, resulting in the above error.

4
| username: gary | Original post link
  1. Stop the replication task
    tiup dmctl --master-addr=masterIP:8261 pause-task dm-task.yaml
  2. Modify the DM task configuration file
  3. Resume the replication task
    tiup dmctl --master-addr=masterIP:8261 resume-task dm-task.yaml
5
| username: forever | Original post link

Check the TiKV logs, there should be other errors reported;
First, troubleshoot according to this guide:

6
| username: HACK | Original post link

Before rebuilding the database, was the data synchronization task thoroughly cleaned up?

7
| username: alfred | Original post link

“[Lightning:Restore:ErrRestoreTable]restore table tidb_X.risk_trendX failed” couldn’t find the table during restore, please check.

8
| username: buchuitoudegou | Original post link

It is probably due to the reason mentioned by Mr. Forever above. It is highly likely that the issue lies with the cluster rather than DM. You should prioritize checking whether the cluster is functioning properly.