update MD by dispatch event pingcap/docs feature/preview-top-navigation

Author: github-actions

markdown-pages/en/tidb/release-8.5/TOC-best-practices.md

@@ -11,6 +11,7 @@
 
 - [Manage DDL](/best-practices/ddl-introduction.md)
 - [Use UUIDs as Primary Keys](/best-practices/uuid.md)
+- [Use TiDB Partitioned Tables](/best-practices/tidb-partitioned-tables-best-practices.md)
 - [Optimize Multi-Column Indexes](/best-practices/multi-column-index-best-practices.md)
 - [Manage Indexes and Identify Unused Indexes](/best-practices/index-management-best-practices.md)
 

markdown-pages/en/tidb/release-8.5/TOC-tidb-releases.md

@@ -12,6 +12,7 @@
 ## RELEASE NOTES
 
 - v8.5
+  - [8.5.5](/releases/release-8.5.5.md)
   - [8.5.4](/releases/release-8.5.4.md)
   - [8.5.3](/releases/release-8.5.3.md)
   - [8.5.2](/releases/release-8.5.2.md)

markdown-pages/en/tidb/release-8.5/TOC.md

@@ -132,6 +132,7 @@
       - [Use Overview](/br/br-use-overview.md)
       - [Snapshot Backup and Restore Guide](/br/br-snapshot-guide.md)
       - [Log Backup and PITR Guide](/br/br-pitr-guide.md)
+      - [Compact Log Backup](/br/br-compact-log-backup.md)
       - [Use Cases](/br/backup-and-restore-use-cases.md)
       - [Backup Storages](/br/backup-and-restore-storages.md)
     - BR CLI Manuals
@@ -749,6 +750,7 @@
       - [`SET ROLE`](/sql-statements/sql-statement-set-role.md)
       - [`SET TRANSACTION`](/sql-statements/sql-statement-set-transaction.md)
       - [`SET <variable>`](/sql-statements/sql-statement-set-variable.md)
+      - [`SHOW AFFINITY`](/sql-statements/sql-statement-show-affinity.md)
       - [`SHOW ANALYZE STATUS`](/sql-statements/sql-statement-show-analyze-status.md)
       - [`SHOW [BACKUPS|RESTORES]`](/sql-statements/sql-statement-show-backups.md)
       - [`SHOW BINDINGS`](/sql-statements/sql-statement-show-bindings.md)
@@ -866,6 +868,7 @@
     - [Temporary Tables](/temporary-tables.md)
     - [Cached Tables](/cached-tables.md)
     - [FOREIGN KEY Constraints](/foreign-key.md)
+    - [Table-Level Data Affinity](/table-affinity.md)
     - Character Set and Collation
       - [Overview](/character-set-and-collation.md)
       - [GBK](/character-set-gbk.md)

markdown-pages/en/tidb/release-8.5/best-practices/massive-regions-best-practices.md

@@ -147,7 +147,7 @@ The default size of a Region is 256 MiB, and you can reduce the number of Region
 
 ### Method 7: Increase the maximum number of connections for Raft communication
 
-By default, the maximum number of connections used for Raft communication between TiKV nodes is 1. Increasing this number can help alleviate blockage issues caused by heavy communication workloads of a large number of Regions. For detailed instructions, see [`grpc-raft-conn-num`](/tikv-configuration-file.md#grpc-raft-conn-num).
+To adjust the maximum number of connections used for Raft communication between TiKV nodes, you can modify the [`server.grpc-raft-conn-num`](/tikv-configuration-file.md#grpc-raft-conn-num) configuration item. Increasing this number can help alleviate blockage issues caused by heavy communication workloads of a large number of Regions.
 
 > **Note:**
 >

markdown-pages/en/tidb/release-8.5/best-practices/pd-scheduling-best-practices.md

@@ -295,7 +295,9 @@ If a TiKV node fails, PD defaults to setting the corresponding node to the **dow
 
 Practically, if a node failure is considered unrecoverable, you can immediately take it offline. This makes PD replenish replicas soon in another node and reduces the risk of data loss. In contrast, if a node is considered recoverable, but the recovery cannot be done in 30 minutes, you can temporarily adjust `max-store-down-time` to a larger value to avoid unnecessary replenishment of the replicas and resources waste after the timeout.
 
-In TiDB v5.2.0, TiKV introduces the mechanism of slow TiKV node detection. By sampling the requests in TiKV, this mechanism works out a score ranging from 1 to 100. A TiKV node with a score higher than or equal to 80 is marked as slow. You can add [`evict-slow-store-scheduler`](/pd-control.md#scheduler-show--add--remove--pause--resume--config--describe) to detect and schedule slow nodes. If only one TiKV is detected as slow, and the slow score reaches the limit (80 by default), the Leader in this node will be evicted (similar to the effect of `evict-leader-scheduler`).
+Starting from TiDB v5.2.0, TiKV introduces a mechanism to detect slow-disk nodes. By sampling the requests in TiKV, this mechanism works out a score ranging from 1 to 100. A TiKV node with a score higher than or equal to 80 is marked as slow. You can add [`evict-slow-store-scheduler`](/pd-control.md#scheduler-show--add--remove--pause--resume--config--describe) to schedule slow nodes. If only one TiKV node is detected as slow, and its slow score reaches the limit (80 by default), the Leaders on that node will be evicted (similar to the effect of `evict-leader-scheduler`).
+
+Starting from v8.5.5, TiKV introduces a mechanism to detect slow-network nodes. Similar to slow-disk node detection, this mechanism identifies slow nodes by probing network latency between TiKV nodes and calculating a score. You can enable this mechanism using [`enable-network-slow-store`](/pd-control.md#scheduler-config-evict-slow-store-scheduler).
 
 > **Note:**
 >

markdown-pages/en/tidb/release-8.5/best-practices/three-nodes-hybrid-deployment.md

@@ -61,7 +61,7 @@ The default value of this parameter is 80% of the number of machine threads. In
 
 #### `server.grpc-concurrency`
 
-This parameter defaults to `4`. Because in the existing deployment plan, the CPU resources are limited and the actual requests are few. You can observe the monitoring panel, lower the value of this parameter, and keep the usage rate below 80%.
+Because in the existing deployment plan, the CPU resources are limited and the actual requests are few. You can observe the monitoring panel, lower the value of [`server.grpc-concurrency`](/tikv-configuration-file.md#grpc-concurrency), and keep the usage rate below 80%.
 
 In this test, the value of this parameter is set to `2`. Observe the **gRPC poll CPU** panel and you can see that the usage rate is just around 80%.