syntax • GET_LOCK and RELEASE_LOCK functions #14994 • LOAD DATA with the REPLACE keyword #24515 • HANDLER statement • CREATE TABLESPACE statement 2.6.2 Features that are different from MySQL 2.6.2.1 Auto-increment when back- ing up data to the network disk built by samba. 6.3.1.6.7 What should I do to handle the rpc error: code = Unavailable desc =... error occurred in BR? This error might occur when the capacity �→ /A | | ￿─ IndexReader_18 root 1 index:StreamAgg_9 �→ 1 time:10.927685ms, �→ loops:2, rpc num: 1, rpc time:10.884355ms, proc keys:25007 206 �→ Bytes N/A | | ￿─ StreamAgg_9 cop 1 funcs:count(1)->

TABLE syntax #4673 • CHECKSUM TABLE syntax #1895 • REPAIR TABLE syntax • OPTIMIZE TABLE syntax • HANDLER statement • CREATE TABLESPACE statement • “Session Tracker: Add GTIDs context to the OK packet” • 300000 | root | | �→ time:43.5ms, loops:294, cop_task: {num: 1, max: 43.1ms, proc_keys: 0, �→ rpc_num: 1, rpc_time: 43ms, copr_cache_hit_ratio: 0.00} �→ �→ | data:TableFullScan_9 353 �→ �→ | 4.58 MB | instances. Each TiKV instance is equipped with 16 CPU cores, 80 GB memory, and 16 threads to process RPC requests (import.num-threads = 16). 934 • 3 TiDB instances. Each TiDB instance is equipped with 16

TABLE syntax #4673 • CHECKSUM TABLE syntax #1895 • REPAIR TABLE syntax • OPTIMIZE TABLE syntax • HANDLER statement • CREATE TABLESPACE statement • “Session Tracker: Add GTIDs context to the OK packet” • 300000 | root | | �→ time:43.5ms, loops:294, cop_task: {num: 1, max: 43.1ms, proc_keys: 0, �→ rpc_num: 1, rpc_time: 43ms, copr_cache_hit_ratio: 0.00} �→ �→ | data:TableFullScan_9 �→ �→ | 4.58 MB | N/A | instances. Each TiKV instance is equipped with 16 CPU cores, 80 GB memory, and 16 threads to process RPC requests (import.num-threads = 16). • 3 TiDB instances. Each TiDB instance is equipped with 16 CPU

blocking users from importing data #42836 @okJiang • Add a retry mechanism when encountering an unknown RPC error during data import #43291 @D3Hunter • Enhance the retry mechanism for Region jobs #43682 @lance6716 enable tidb_pessimistic_txn_fair_locking, in some extreme cases, expired requests caused by failed RPC retries might affect data correctness during the resolve lock operation #14551 @MyonKeminta • Fix enable tidb_pessimistic_txn_fair_locking, in some extreme cases, expired requests caused by failed RPC retries might cause transaction conflicts to be ignored, thus affecting transaction consistency #14311

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 6729 17.14.4 Remote Procedure Call (RPC)· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 6729 17.14.5 Request Unit (RU)· migration. 42 Parallel mode for TSO requests In high-concurrency scenarios, you can specific period and processes them in batches serially to decrease the number of Remote Procedure Call (RPC) requests and reduce PD workload. In latency-sensitive scenarios, however, the performance of this

migration. 37 Parallel mode for TSO requests In high-concurrency scenarios, you can specific period and processes them in batches serially to decrease the number of Remote Procedure Call (RPC) requests and reduce PD workload. In latency-sensitive scenarios, however, the performance of this retrieval latency but might in- crease the PD workload. To set a parallel RPC mode for retrieving TSO, configure the tidb_tso_client_rpc_mode system variable. For more information, see documentation. • Optimize

item is deprecated. The new version of the Region replica selector is used by default when sending RPC requests to TiKV. • Starting from v8.2.0, the BR snapshot restore parameter --concurrency is dep- TABLE syntax #4673 • CHECKSUM TABLE syntax #1895 • REPAIR TABLE syntax • OPTIMIZE TABLE syntax • HANDLER statement • CREATE TABLESPACE statement • “Session Tracker: Add GTIDs context to the OK packet” • 300000 | root | | �→ time:43.5ms, loops:294, cop_task: {num: 1, max: 43.1ms, proc_keys: 0, �→ rpc_num: 1, rpc_time: 43ms, copr_cache_hit_ratio: 0.00} �→ �→ | data:TableFullScan_9 �→ �→ | 4.58 MB | N/A |

TABLE syntax #4673 • CHECKSUM TABLE syntax #1895 • REPAIR TABLE syntax • OPTIMIZE TABLE syntax • HANDLER statement • CREATE TABLESPACE statement • “Session Tracker: Add GTIDs context to the OK packet” • 300000 | root | | �→ time:43.5ms, loops:294, cop_task: {num: 1, max: 43.1ms, proc_keys: 0, �→ rpc_num: 1, rpc_time: 43ms, copr_cache_hit_ratio: 0.00} �→ �→ | data:TableFullScan_9 �→ �→ | 4.58 MB | N/A | configuration, so manual configuration is unnecessary. If the TiKV- Details > Backup & Import > Import RPC count monitoring metric in Grafana shows that the number of files BR downloads remains close to 0 for

TABLE syntax #4673 • CHECKSUM TABLE syntax #1895 • REPAIR TABLE syntax • OPTIMIZE TABLE syntax • HANDLER statement • CREATE TABLESPACE statement • “Session Tracker: Add GTIDs context to the OK packet” • 300000 | root | | �→ time:43.5ms, loops:294, cop_task: {num: 1, max: 43.1ms, proc_keys: 0, �→ rpc_num: 1, rpc_time: 43ms, copr_cache_hit_ratio: 0.00} �→ �→ | data:TableFullScan_9 �→ �→ | 4.58 MB | N/A | configuration, so manual configuration is unnecessary. If the TiKV- Details > Backup & Import > Import RPC count monitoring metric in Grafana shows that the number of files BR downloads remains close to 0 for

-v2 Newly added Controls whether to use the new version of the Region replica selector when sending RPC requests to TiKV. The default value is true. TiKV log- �→ backup �→ . �→ initial �→ - �→ scan �→ - TABLE syntax #4673 • CHECKSUM TABLE syntax #1895 • REPAIR TABLE syntax • OPTIMIZE TABLE syntax • HANDLER statement • CREATE TABLESPACE statement • “Session Tracker: Add GTIDs context to the OK packet” • 300000 | root | | �→ time:43.5ms, loops:294, cop_task: {num: 1, max: 43.1ms, proc_keys: 0, �→ rpc_num: 1, rpc_time: 43ms, copr_cache_hit_ratio: 0.00} �→ �→ | data:TableFullScan_9 368 �→ �→ | 4.58 MB |