importing a large amount of data and quickly initializing a specific table in a TiDB cluster Support checkpoints to store the import progress, so that tidb-lightning continues importing from where it lefts off recommended that you understand how to handle checkpoints, and then choose the appropriate way to proceed according to your needs. 243 5.3.5.3.1 Checkpoints Migrating a large volume of data usually takes imported. Fortunately, TiDB Lightning provides a feature called checkpoints, which makes TiDB Lightning save the import progress as checkpoints from time to time, so that an interrupted import task can be

based on binlog positions and the binlog file size, and store the replicated binlog positions as checkpoints. However, the official MySQL uses uint32 to store binlog positions, which means the binlog position there might be chances that you need to reimport from scratch, because there is no guarantee that checkpoints work across versions. 11.8.4 TiDB Lightning Prechecks Starting from TiDB 5.3.0, TiDB Lightning key of this service. ### key-path = "/path/to/lightning.key" [checkpoint] ### Whether to enable checkpoints. ### While importing data, TiDB Lightning records which tables have been �→ imported, so ###

based on binlog positions and the binlog file size, and store the replicated binlog positions as checkpoints. However, the official MySQL uses uint32 to store binlog positions, which means the binlog position there might be chances that you need to reimport from scratch, because there is no guarantee that checkpoints work across versions. 11.8.4 TiDB Lightning Configuration This document provides samples for key of this service. ### key-path = "/path/to/lightning.key" [checkpoint] ### Whether to enable checkpoints. ### While importing data, TiDB Lightning records which tables have been �→ imported, so ###

based on binlog positions and the binlog file size, and store the replicated binlog positions as checkpoints. However, the official MySQL uses uint32 to store binlog positions, which means the binlog position there might be chances that you need to reimport from scratch, because there is no guarantee that checkpoints work across versions. 11.8.4 TiDB Lightning Configuration This document provides samples for key of this service. ### key-path = "/path/to/lightning.key" [checkpoint] ### Whether to enable checkpoints. ### While importing data, TiDB Lightning records which tables have been �→ imported, so ###

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2069 13.7.10 TiDB Lightning Checkpoints · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2074 13.7.11 Use TiDB importing a large amount of data and quickly initializing a specific table in a TiDB cluster Support checkpoints to store the import progress, so that tidb-lightning continues importing from where it lefts off recommended that you understand how to handle checkpoints, and then choose the appropriate way to proceed according to your needs. 681 6.3.5.3.1 Checkpoints Migrating a large volume of data usually takes

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2472 13.7.10 TiDB Lightning Checkpoints · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2477 13.7.11 Use TiDB owner node is restarted or changed due to failures, TiDB can 40 still recover progress from checkpoints that are automatically updated on a regular basis, making the DDL execution more stable and efficient a large amount of data and quickly initializing a specific table in a TiDB cluster • Support checkpoints to store the import progress, so that tidb-lightning con- tinues importing from where it lefts

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2391 13.7.10 TiDB Lightning Checkpoints · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2396 13.7.11 Use TiDB dedicated thread to reduce TiCDC replication latency #13774 @overvenus • Support pull model for Checkpoints #13824 @YuJuncen • Avoid spinning issues on the sender side by updating crossbeam-channel #13815 importing a large amount of data and quickly initializing a specific table in a TiDB cluster Support checkpoints to store the import progress, so that tidb-lightning continues importing from where it lefts off

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2530 13.7.10 TiDB Lightning Checkpoints · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2535 13.7.11 Use TiDB a large amount of data and quickly initializing a specific table in a TiDB cluster • Support checkpoints to store the import progress, so that tidb-lightning con- tinues importing from where it lefts checkpoint For importing a large volume of data, it is essential to refer to Lightning Checkpoints and enable checkpoints. It is recommended to prioritize using MySQL as the driver to avoid losing the checkpoint

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2509 13.7.10 TiDB Lightning Checkpoints · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 2514 13.7.11 Use TiDB a large amount of data and quickly initializing a specific table in a TiDB cluster • Support checkpoints to store the import progress, so that tidb-lightning con- tinues importing from where it lefts checkpoint For importing a large volume of data, it is essential to refer to Lightning Checkpoints and enable checkpoints. It is recommended to prioritize using MySQL as the driver to avoid losing the checkpoint

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3059 13.7.12 TiDB Lightning Checkpoints · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3064 13.7.13 Use TiDB checkpoint information about the restore progress to the backup storage system during restore. These checkpoints enable quick resumption of interrupted restores. Starting from v8.4.0, BR writes restore checkpoint a large amount of data and quickly initializing a specific table in a TiDB cluster • Support checkpoints to store the import progress, so that tidb-lightning con- tinues importing from where it lefts