�→ local", you must specify status-port and pd-addr correctly. Otherwise �→ , the import will be abnormal. [tikv-importer] ### "local": Default backend. The local backend is recommended to import �→ large = "local", you must specify status-port and pd- �→ addr correctly. Otherwise, the import will be abnormal. For more information on TiDB Lightning configuration, refer to TiDB Lightning Con- figuration = "local", you must specify status-port and pd-addr �→ correctly. Otherwise, the import will be abnormal. For more information on the configuration file, refer to TiDB Lightning Configuration. 5.3.6

fix unhealthy regions before other operations.” prompt, some Regions in the current cluster are abnormal. You need to troubleshoot the anomalies until the check result becomes “All Regions are healthy” for data restore at the same time, these configurations might be mistakenly overwritten and cause abnormal cluster status. • BR consumes a lot of cluster resources to restore data, so in fact, running BR (Garbage Collection) status is normal by viewing the time when the last GC happens. If the GC is abnormal, it might lead to excessive historical data, thereby decreasing the access efficiency. 289 6.6

imported includes an auto-increment column of the double type, the auto_increment value becomes abnormal #1178 – Backup & Restore (BR) * Fix the issue of backup interruption caused by the failure of fix unhealthy regions before other operations.” prompt, some Regions in the current cluster are abnormal. You need to troubleshoot the anomalies until the check result becomes “All Regions are healthy” (Garbage Collection) status is normal by viewing the time when the last GC happens. If the GC is abnormal, it might lead to excessive historical data, thereby decreasing the access efficiency. 258 6.6

internally packages the table creation and deletion statements and adds judgment logic to prevent abnormal interruption of business pro- cesses. • Details: create table if not exists table_name or drop drop table if exists �→ table_name statements are recommended to add if judgments to avoid abnormal interruptions caused by SQL commands running abnormally on the application side. 4.11.2.2.2 SELECT * usage �→ local", you must specify status-port and pd-addr correctly. Otherwise �→ , the import will be abnormal. [tikv-importer] ### "local": Default backend. The local backend is recommended to import �→ large

fix unhealthy regions before other operations.” prompt, some Regions in the current cluster are abnormal. You need to troubleshoot the anomalies until the check result becomes “All Regions are healthy” (Garbage Collection) status is normal by viewing the time when the last GC happens. If the GC is abnormal, it might lead to excessive historical data, thereby decreasing the access efficiency. 272 6.6 fies with PD whether it has been deleted. 293 Configuration item Description raftstore �→ . �→ abnormal �→ - �→ leader �→ - �→ missing �→ - �→ duration �→ The nor- mal dura- tion al- lowed for a peer

mechanism for TiFlash nodes in the TiFlash MPP mode to mitigate the performance impact when nodes are abnormal #39686 @hackersean • TiKV • Stop writing to Raft Engine when there is insufficient space to avoid internally packages the table creation and deletion statements and adds judgment logic to prevent abnormal interruption of business pro- cesses. • Details: create table if not exists table_name or drop drop table if exists �→ table_name statements are recommended to add if judgments to avoid abnormal interruptions caused by SQL commands running abnormally on the application side. 4.11.2.2.2 SELECT * usage

internally packages the table creation and deletion statements and adds judgment logic to prevent abnormal interruption of business pro- cesses. • Details: create table if not exists table_name or drop drop table if exists �→ table_name statements are recommended to add if judgments to avoid abnormal interruptions caused by SQL commands running abnormally on the application side. 4.11.2.2.2 SELECT * usage = "local", you must specify status-port and pd- �→ addr correctly. Otherwise, the import will be abnormal. For more information on TiDB Lightning configuration, refer to TiDB Lightning Con- figuration

@YuJuncen • PD • Fix the issue that the number of low space store in the PD monitoring panel is abnormal after TiKV panics #6252 @HuSharp • Fix the issue that Region Health monitoring data is deleted internally packages the table creation and deletion statements and adds judgment logic to prevent abnormal interruption of business pro- cesses. • Details: create table if not exists table_name or drop drop table if exists �→ table_name statements are recommended to add if judgments to avoid abnormal interruptions caused by SQL commands running abnormally on the application side. 4.11.2.2.2 SELECT * usage

internally packages the table creation and deletion statements and adds judgment logic to prevent abnormal interruption of business pro- cesses. • Details: create table if not exists table_name or drop drop table if exists �→ table_name statements are recommended to add if judgments to avoid abnormal interruptions caused by SQL commands running abnormally on the application side. 4.11.2.2.2 SELECT * usage = "local", you must specify status-port and pd- �→ addr correctly. Otherwise, the import will be abnormal. For more information on TiDB Lightning configuration, refer to TiDB Lightning Con- figuration