restoration. In v7.6.0, BR optimizes the Region scattering algorithm, which quickly splits the restore task into a large num- ber of small tasks and scatters them to all TiKV nodes in batches. The new parallel �→ changefeed_id}/synced to query the downstream synchronization status of a specified replication task (changefeed). By using this API, you can determine whether the upstream data received by TiCDC has on read latency #8583 @JaySon- Huang • Reduce the impact of background GC tasks on read and write task latency #8650 @JaySon-Huang • Support merging identical data reading operations in a storage-compute

tasks as well. In v7.4.0, Resource Control now identifies �→ and manages the priority of background task execution, such as auto- �→ analyze, Backup & Restore, bulk load with TiDB Lightning, and online �→ TiDB nodes can execute the same DDL task in parallel under the DXF. Starting from v7.2.0, the DXF supports multiple TiDB nodes to execute the same IMPORT INTO task in parallel, thereby better utilizing improve the performance of these tasks. To use the DXF, set tidb_enable_dist_task value to ON. SET GLOBAL tidb_enable_dist_task = ON; For more information, see documentation. • Improve the performance

Lightning task-info- �→ schema- �→ name Newly added Specifies the name of the database where duplicated data is stored when TiDB Lightning detects conflicts. By default, the value is “light- ning_task_info” compatibility issue of sql mode #3810 * Fix the potential panic issue that occurs when a replication task is removed #3128 * Fix the issue of panic and data inconsistency that occurs when outputting the replication task to get stuck #4055 * Fix the issue that no log is output when the disk is fully written #3362 * Fix the issue that special comments in DDL statements cause the replication task to stop #3755

@gmhdbjd TiDB can filter out binlog events of the schemas and tables that are not in the migration task, thus improving the parsing efficiency and stability. This policy takes effect by default in v6.5 not support parsing, the task will fail. By only parsing the binlog events of the tables in the migration task, the binlog parsing efficiency can be greatly improved and the task stability can be enhanced recovery) either. When using the index acceleration feature, you need to make sure that no PITR backup task is running in the background; otherwise, unexpected results might occur. For more information, see

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 4625 14.21.1 TiDB Backend Task Distributed Execution Framework· · · · · · · · · · · · · · 4625 15 FAQs 4629 15.1 TiDB FAQ Summary· in the new distributed parallel execution framework, multiple TiDB nodes can execute the same DDL task in parallel, thus better utilizing the resources of the TiDB cluster and significantly improving the operations. To use the distributed framework, set the value of tidb_enable_dist_task to ON: SET GLOBAL tidb_enable_dist_task = ON; For more information, see documentation. 2.2.1.2 Reliability • Resource

I handle the Error 1298: Unknown or incorrect time zone: 'UTC' error when creating the replication task or replicating data to MySQL? · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1194 7.6.4 The start-ts timestamp of the TiCDC task is quite different from the current time. During the execution of this task, replication is in- terrupted and an error [CDC:ErrBufferReachLimit] 1197 7.7.1 How do I choose start-ts when creating a task in TiCDC? · · · · · · · · · 1197 7.7.2 Why can’t some tables be replicated when I create a task in TiCDC? · 1198 7.7.3 How do I view the state of

resource consumption based on the �→ needs of different application systems. This keeps background task �→ consumption at a low level and ensures the quality of online services �→ . 0 码力 | 6705 页 | 110.86 MB | 9 月前

3

replaced, and both versions of data are stored. The old data is cleaned up by the Garbage Collection (GC) task periodically, which helps reclaim storage space to im- prove the performance and stability of the execution, the GC task is delayed. To ensure that the GC task is not delayed indefinitely, TiDB introduces the system vari- able tidb_gc_max_wait_time to control the maximum delay time of the GC task. If the maximum Before TiDB v6.1.0, the SHOW ANALYZE STATUS statement shows instance- level tasks only, and history task records are cleared after a TiDB restart. Therefore, you cannot view history statistics collection

consistent with the maximum number of conflicting records that can be tolerated in a single import task. • The following features are planned for removal in future versions: • Starting from v8.0.0, TiDB -----------------------------------------------+----------+------+ �→ | id | estRows | actRows | task | access object | �→ execution info �→ �→ | operator info �→ �→ | memory | disk | +-- �→ ---- concurrency:5, task_num:293, tot_wait:262.536669ms, tot_exec �→ :40.171833ms, tot_time:302.827753ms, max:60.636886ms, p95:60.636886ms �→ }, final_worker:{wall_time:60.701437ms, concurrency:5, task_num:25, �→

that an ADD INDEX or IMPORT INTO task is executed only by one TiDB node by default. Starting from v8.1.0, TiDB enables this feature by default (tidb_enable_dist_task defaults to ON). When enabled, the the DXF can schedule multiple TiDB nodes to execute the same ADD INDEX or IMPORT INTO task in parallel, fully utilizing the resources of the TiDB cluster and greatly improving the performance of these tasks �→ to (0, 1] �→ . 45 Variable name Change type Description tidb_ �→ enable �→ _ �→ dist �→ _ �→ task Modified Changes the default value from OFF to ON. This means that Dis- tributed eXecu- tion Frame-