Issues with Importing After Exporting Using Dumpling

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

Original topic: dumpling导出后再导入问题

| username: l940399478

After exporting data from version 4.0.14 using Dumpling, it needs to be imported into a running TiDB cluster of version 6.5.2. However, directly using TiDB Lightning for import will affect the normal use of the TiDB version 6.5.2. Is there any other way?

| username: 芮芮是产品 | Original post link

No, you just need to enable traffic limiting.

| username: xingzhenxiang | Original post link

Logical import, appropriately control region-concurrency.

| username: zhanggame1 | Original post link

tidb-lightning has two modes: physical import mode and logical import mode. The default physical mode has a significant impact, so use the logical mode for import.

| username: l940399478 | Original post link

Can you recommend a commonly used configuration file for tidb-lightning?

| username: zhanggame1 | Original post link

Use the official documentation to make the change
TiDB Lightning Tutorial | PingCAP Documentation Center
backend = “local” to “tidb”

| username: dba远航 | Original post link

Importing during idle business hours should not be an issue. Isn’t this how it’s usually done in production?

| username: 普罗米修斯 | Original post link


region-concurrency = 16

max-size = 256

max-days = 28

max-backups = 14

level = “info”

status-addr = ‘:8289’

check-requirements = true

file = “/home/tidb/tidb-toolkit-v5.0.1-linux-amd64/bin/tidb-lightning.log”


backend = “tidb”

on-duplicate = “replace”


data-source-dir = “/data”


host = “tidb-ip-x.x.x.x”

port = 4000

user = “root”

password = “*****”

status-port = 10080

| username: system | Original post link

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