Encountering Errors in Lighting Physics Import and Handling the Job Later

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

Original topic: lighting物理导入遇到meet error and handle the job later

| username: xingzhenxiang

[Test Environment for TiDB]
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

Encountered an issue with physical import using Lightning
meet error and handle the job later
put job back to jobCh to retry later
BR:Restore:ErrRestoreSplitFailed] fail to split region

| username: xingzhenxiang | Original post link

How to operate?

| username: dba远航 | Original post link

REGINE partitioning failed, check TIKV.

| username: xingzhenxiang | Original post link

How to check data import, please provide a reference, thank you.

| username: 有猫万事足 | Original post link

It would be best if you could post the logs, as the current information is a bit limited.

  log.Error("fail to split region",
  	logutil.Region(regionInfo.Region),
  	logutil.Key("key", key),
  	zap.Stringer("regionErr", resp.RegionError))

It seems like the previous part should give you some information about the region/key.

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

Just run the lightning command again.

| username: xingzhenxiang | Original post link

Here is the error message
related_error.txt (120.2 KB)

| username: WalterWj | Original post link

This is normal. The lightning task will retry on its own. It might be due to high pressure on the TiDB cluster, causing the region to not split successfully as expected.

| username: xingzhenxiang | Original post link

Thank you for your reply.

| username: system | Original post link

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