Revert "Merge remote-tracking branch 'upstream/master' into rn-9.0.0"

This reverts commit 04c337e, reversing
changes made to 1a05ab8.

Author: hfxsd

.github/workflows/doc_review.yml

@@ -76,7 +76,7 @@ jobs:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           API_PROVIDER: "openai"  # or "openai" if you want to use OpenAI
           OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
-          OPENAI_API_MODEL: "gpt-4o"
+          OPENAI_API_MODEL: "gpt-4"
           exclude: "**/*.json"  # Optional: exclude patterns separated by commas
           REVIEW_MODE: ${{ steps.extract.outputs.REVIEW_MODE || 'default' }}
           COMMIT_SHA: ${{ steps.extract.outputs.COMMIT_SHA || '' }}

TOC.md

@@ -280,37 +280,6 @@
   - [Monitoring API](/tidb-monitoring-api.md)
   - [Deploy Monitoring Services](/deploy-monitoring-services.md)
   - [Upgrade Monitoring Services](/upgrade-monitoring-services.md)
-  - TiDB Dashboard
-    - [Overview](/dashboard/dashboard-intro.md)
-    - Maintain
-      - [Deploy](/dashboard/dashboard-ops-deploy.md)
-      - [Reverse Proxy](/dashboard/dashboard-ops-reverse-proxy.md)
-      - [User Management](/dashboard/dashboard-user.md)
-      - [Secure](/dashboard/dashboard-ops-security.md)
-    - [Access](/dashboard/dashboard-access.md)
-    - [Overview Page](/dashboard/dashboard-overview.md)
-    - [Cluster Info Page](/dashboard/dashboard-cluster-info.md)
-    - [Top SQL Page](/dashboard/top-sql.md)
-    - [Key Visualizer Page](/dashboard/dashboard-key-visualizer.md)
-    - [Metrics Relation Graph](/dashboard/dashboard-metrics-relation.md)
-    - SQL Statements Analysis
-      - [SQL Statements Page](/dashboard/dashboard-statement-list.md)
-      - [SQL Details Page](/dashboard/dashboard-statement-details.md)
-    - [Slow Queries Page](/dashboard/dashboard-slow-query.md)
-    - Cluster Diagnostics
-      - [Access Cluster Diagnostics Page](/dashboard/dashboard-diagnostics-access.md)
-      - [View Diagnostics Report](/dashboard/dashboard-diagnostics-report.md)
-      - [Use Diagnostics](/dashboard/dashboard-diagnostics-usage.md)
-    - [Monitoring Page](/dashboard/dashboard-monitoring.md)
-    - [Search Logs Page](/dashboard/dashboard-log-search.md)
-    - [Resource Manager Page](/dashboard/dashboard-resource-manager.md)
-    - Instance Profiling
-      - [Manual Profiling](/dashboard/dashboard-profiling.md)
-      - [Continuous Profiling](/dashboard/continuous-profiling.md)
-    - Session Management and Configuration
-      - [Share Session](/dashboard/dashboard-session-share.md)
-      - [Configure SSO](/dashboard/dashboard-session-sso.md)
-    - [FAQ](/dashboard/dashboard-faq.md)
   - [Export Grafana Snapshots](/exporting-grafana-snapshots.md)
   - [TiDB Cluster Alert Rules](/alert-rules.md)
   - [TiFlash Alert Rules](/tiflash/tiflash-alert-rules.md)
@@ -808,7 +777,6 @@
       - [`BEGIN`](/sql-statements/sql-statement-begin.md)
       - [`CALIBRATE RESOURCE`](/sql-statements/sql-statement-calibrate-resource.md)
       - [`CANCEL IMPORT JOB`](/sql-statements/sql-statement-cancel-import-job.md)
-      - [`CANCEL TRAFFIC JOBS`](/sql-statements/sql-statement-cancel-traffic-jobs.md)
       - [`COMMIT`](/sql-statements/sql-statement-commit.md)
       - [`CREATE BINDING`](/sql-statements/sql-statement-create-binding.md)
       - [`CREATE DATABASE`](/sql-statements/sql-statement-create-database.md)
@@ -915,16 +883,13 @@
       - [`SHOW TABLE REGIONS`](/sql-statements/sql-statement-show-table-regions.md)
       - [`SHOW TABLE STATUS`](/sql-statements/sql-statement-show-table-status.md)
       - [`SHOW TABLES`](/sql-statements/sql-statement-show-tables.md)
-      - [`SHOW TRAFFIC JOBS`](/sql-statements/sql-statement-show-traffic-jobs.md)
       - [`SHOW VARIABLES`](/sql-statements/sql-statement-show-variables.md)
       - [`SHOW WARNINGS`](/sql-statements/sql-statement-show-warnings.md)
       - [`SHUTDOWN`](/sql-statements/sql-statement-shutdown.md)
       - [`SPLIT REGION`](/sql-statements/sql-statement-split-region.md)
       - [`START TRANSACTION`](/sql-statements/sql-statement-start-transaction.md)
       - [`TABLE`](/sql-statements/sql-statement-table.md)
       - [`TRACE`](/sql-statements/sql-statement-trace.md)
-      - [`TRAFFIC CAPTURE`](/sql-statements/sql-statement-traffic-capture.md)
-      - [`TRAFFIC REPLAY`](/sql-statements/sql-statement-traffic-replay.md)
       - [`TRUNCATE`](/sql-statements/sql-statement-truncate.md)
       - [`UNLOCK STATS`](/sql-statements/sql-statement-unlock-stats.md)
       - [`UPDATE`](/sql-statements/sql-statement-update.md)
@@ -1069,12 +1034,43 @@
     - [Metadata Lock](/metadata-lock.md)
     - [TiDB Accelerated Table Creation](/accelerated-table-creation.md)
     - [Schema Cache](/schema-cache.md)
+  - UI
+    - TiDB Dashboard
+      - [Overview](/dashboard/dashboard-intro.md)
+      - Maintain
+        - [Deploy](/dashboard/dashboard-ops-deploy.md)
+        - [Reverse Proxy](/dashboard/dashboard-ops-reverse-proxy.md)
+        - [User Management](/dashboard/dashboard-user.md)
+        - [Secure](/dashboard/dashboard-ops-security.md)
+      - [Access](/dashboard/dashboard-access.md)
+      - [Overview Page](/dashboard/dashboard-overview.md)
+      - [Cluster Info Page](/dashboard/dashboard-cluster-info.md)
+      - [Top SQL Page](/dashboard/top-sql.md)
+      - [Key Visualizer Page](/dashboard/dashboard-key-visualizer.md)
+      - [Metrics Relation Graph](/dashboard/dashboard-metrics-relation.md)
+      - SQL Statements Analysis
+        - [SQL Statements Page](/dashboard/dashboard-statement-list.md)
+        - [SQL Details Page](/dashboard/dashboard-statement-details.md)
+      - [Slow Queries Page](/dashboard/dashboard-slow-query.md)
+      - Cluster Diagnostics
+        - [Access Cluster Diagnostics Page](/dashboard/dashboard-diagnostics-access.md)
+        - [View Diagnostics Report](/dashboard/dashboard-diagnostics-report.md)
+        - [Use Diagnostics](/dashboard/dashboard-diagnostics-usage.md)
+      - [Monitoring Page](/dashboard/dashboard-monitoring.md)
+      - [Search Logs Page](/dashboard/dashboard-log-search.md)
+      - [Resource Manager Page](/dashboard/dashboard-resource-manager.md)
+      - Instance Profiling
+        - [Manual Profiling](/dashboard/dashboard-profiling.md)
+        - [Continuous Profiling](/dashboard/continuous-profiling.md)
+      - Session Management and Configuration
+        - [Share Session](/dashboard/dashboard-session-share.md)
+        - [Configure SSO](/dashboard/dashboard-session-sso.md)
+      - [FAQ](/dashboard/dashboard-faq.md)
   - [Telemetry](/telemetry.md)
   - [Error Codes](/error-codes.md)
   - [Table Filter](/table-filter.md)
   - [Schedule Replicas by Topology Labels](/schedule-replicas-by-topology-labels.md)
   - [URI Formats of External Storage Services](/external-storage-uri.md)
-  - [TiDB Workload Repository](/workload-repository.md)
 - FAQs
   - [FAQ Summary](/faq/faq-overview.md)
   - [TiDB FAQs](/faq/tidb-faq.md)

_index.md

@@ -82,7 +82,7 @@ summary: TiDB is an open-source distributed SQL database that supports Hybrid Tr
 
 <LearningPath label="Monitor" icon="cloud6">
 
-[Use Prometheus, Grafana, and TiDB Dashboard](https://docs.pingcap.com/tidb/dev/tidb-monitoring-framework)
+[Use Prometheus and Grafana](https://docs.pingcap.com/tidb/dev/tidb-monitoring-framework)
 
 [Monitoring API](https://docs.pingcap.com/tidb/dev/tidb-monitoring-api)
 

basic-features.md

@@ -28,7 +28,7 @@ You can try out TiDB features on [TiDB Playground](https://play.tidbcloud.com/?u
 | [Date and time types](/data-type-date-and-time.md) | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
 | [String types](/data-type-string.md) | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
 | [JSON type](/data-type-json.md) | Y | Y | Y | Y | Y | E | E | E | E | E |
-| [Vector types](/vector-search/vector-search-data-types.md) | E | N | N | N | N | N | N | N | N | N |
+| [Vectort types](/vector-search/vector-search-data-types.md) | E | N | N | N | N | N | N | N | N | N |
 | [Control flow functions](/functions-and-operators/control-flow-functions.md) | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
 | [String functions](/functions-and-operators/string-functions.md) | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
 | [Numeric functions and operators](/functions-and-operators/numeric-functions-and-operators.md) | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |

benchmark/benchmark-tidb-using-tpcc.md

@@ -24,7 +24,7 @@ Before testing, TPC-C Benchmark specifies the initial state of the database, whi
 * The `DISTRICT` table has W \* 10 records (Each warehouse provides services to 10 districts)
 * The `CUSTOMER` table has W \* 10 \* 3,000 records (Each district has 3,000 customers)
 * The `HISTORY` table has W \* 10 \* 3,000 records (Each customer has one transaction history)
-* The `ORDER` table has W \* 10 \* 3,000 records (Each district has 3,000 orders and the last 900 orders generated are added to the `NEW-ORDER` table. Each order randomly generates 5 ~ 15 ORDER-LINE records.)
+* The `ORDER` table has W \* 10 \* 3,000 records (Each district has 3,000 orders and the last 900 orders generated are added to the `NEW-ORDER` table. Each order randomly generates 5 ~ 15 ORDER-LINE records.
 
 In this document, the testing uses 1,000 warehouses as an example to test TiDB.
 

best-practices/java-app-best-practices.md

@@ -204,62 +204,26 @@ Through monitoring, you might notice that although the application only performs
 
 After it is configured, you can check the monitoring to see a decreased number of `SELECT` statements.
 
-> **Note:**
->
-> Enabling `useConfigs=maxPerformance` requires MySQL Connector/J version 8.0.33 or later. For more details, see [MySQL JDBC Bug](/develop/dev-guide-third-party-tools-compatibility.md#mysql-jdbc-bugs).
-
 #### Timeout-related parameters
 
 TiDB provides two MySQL-compatible parameters that controls the timeout: `wait_timeout` and `max_execution_time`. These two parameters respectively control the connection idle timeout with the Java application and the timeout of the SQL execution in the connection; that is to say, these parameters control the longest idle time and the longest busy time for the connection between TiDB and the Java application. The default value of both parameters is `0`, which by default allows the connection to be infinitely idle and infinitely busy (an infinite duration for one SQL statement to execute).
 
 However, in an actual production environment, idle connections and SQL statements with excessively long execution time negatively affect databases and applications. To avoid idle connections and SQL statements that are executed for too long, you can configure these two parameters in your application's connection string. For example, set `sessionVariables=wait_timeout=3600` (1 hour) and `sessionVariables=max_execution_time=300000` (5 minutes).
 
-#### Typical JDBC connection string parameters
-
-Combining the preceding parameter values, the JDBC connection string configuration is as follows:
-
-```
-jdbc:mysql://<IP_ADDRESS>:<PORT_NUMBER>/<DATABASE_NAME>?characterEncoding=UTF-8&useSSL=false&useServerPrepStmts=true&cachePrepStmts=true&prepStmtCacheSqlLimit=10000&prepStmtCacheSize=1000&useConfigs=maxPerformance&rewriteBatchedStatements=true
-```
-
-> **Note:**
->
-> If you are connecting over a public network, you need to set `useSSL=true` and [enable TLS between TiDB clients and servers](/enable-tls-between-clients-and-servers.md).
-
 ## Connection pool
 
 Building TiDB (MySQL) connections is relatively expensive (for OLTP scenarios at least), because in addition to building a TCP connection, connection authentication is also required. Therefore, the client usually saves the TiDB (MySQL) connections to the connection pool for reuse.
 
-TiDB supports the following Java connection pools:
-
-- [HikariCP](https://github.com/brettwooldridge/HikariCP)
-- [tomcat-jdbc](https://tomcat.apache.org/tomcat-10.1-doc/jdbc-pool)
-- [druid](https://github.com/alibaba/druid)
-- [c3p0](https://www.mchange.com/projects/c3p0/)
-- [dbcp](https://commons.apache.org/proper/commons-dbcp/)
+Java has many connection pool implementations such as [HikariCP](https://github.com/brettwooldridge/HikariCP), [tomcat-jdbc](https://tomcat.apache.org/tomcat-10.1-doc/jdbc-pool.html), [druid](https://github.com/alibaba/druid), [c3p0](https://www.mchange.com/projects/c3p0/), and [dbcp](https://commons.apache.org/proper/commons-dbcp/). TiDB does not limit which connection pool you use, so you can choose whichever you like for your application.
 
-In practice, some connection pools might persistently use specific active sessions. Although the total number of connections appears evenly distributed across TiDB compute nodes, uneven distribution of active connections can lead to actual load imbalance. In distributed scenarios, it is recommended to use HikariCP, which manages connection lifecycles effectively and helps prevent active connections from being fixed on certain nodes, achieving balanced load distribution.
+### Configure the number of connections
 
-### Typical connection pool configuration
-
-The following is an example configuration for HikariCP:
-
-```yaml
-hikari:
-  maximumPoolSize: 20
-  poolName: hikariCP
-  connectionTimeout: 30000 
-  maxLifetime: 1200000
-  keepaliveTime: 120000
-```
+It is a common practice that the connection pool size is well adjusted according to the application's own needs. Take HikariCP as an example:
 
-The parameter explanations are as follows. For more details, refer to the [official HikariCP documentation](https://github.com/brettwooldridge/HikariCP/blob/dev/README.md).
+- `maximumPoolSize`: The maximum number of connections in the connection pool. If this value is too large, TiDB consumes resources to maintain useless connections. If this value is too small, the application gets slow connections. So configure this value for your own good. For details, see [About Pool Sizing](https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing).
+- `minimumIdle`: The minimum number of idle connections in the connection pool. It is mainly used to reserve some connections to respond to sudden requests when the application is idle. You can also configure it according to your application needs.
 
-- `maximumPoolSize`: the maximum number of connections in the pool. The default value is `10`. In containerized environments, it is recommended to set this to 4–10 times the number of CPU cores available to the Java application. Setting this value too high can lead to resource wastage, while setting it too low can slow down connection acquisition. See [About Pool Sizing](https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing) for more details.
-- `minimumIdle`: HikariCP recommends not setting this parameter. The default value is equal to the value of `maximumPoolSize`, which disables connection pool scaling. This ensures that connections are readily available during traffic spikes and avoids delays caused by connection creation.
-- `connectionTimeout`: the maximum time (in milliseconds) that an application waits to acquire a connection from the pool. The default value is `30000` milliseconds (30 seconds). If no available connection is obtained within this time, a `SQLException` exception occurs.
-- `maxLifetime`: the maximum lifetime (in milliseconds) of a connection in the pool. The default value is `1800000` milliseconds (30 minutes). Connections in use are not affected. After the connection is closed, it will be removed according to this setting. Setting this value too low can cause frequent reconnections. If you are using [`graceful-wait-before-shutdown`](/tidb-configuration-file.md#graceful-wait-before-shutdown-new-in-v50), ensure this value is less than the wait time.
-- `keepaliveTime`: the interval (in milliseconds) between keepalive operations on connections in the pool. This setting helps prevent disconnections caused by database or network idle timeouts. The default value is `120000` milliseconds (2 minutes). The pool prefers using the JDBC4 `isValid()` method to keep idle connections alive.
+The application needs to return the connection after finishing using it. It is also recommended that the application use the corresponding connection pool monitoring (such as `metricRegistry`) to locate the connection pool issue in time.
 
 ### Probe configuration
 

best-practices/three-nodes-hybrid-deployment.md

@@ -69,7 +69,7 @@ In this test, the value of this parameter is set to `2`. Observe the **gRPC poll
 
 #### `storage.scheduler-worker-pool-size`
 
-When TiKV detects that the CPU core number of the machine is greater than or equal to `16`, this parameter value defaults to `8`. When the CPU core number is smaller than `16`, the parameter value defaults to `4`. This parameter is used when TiKV converts complex transaction requests to simple key-value reads or writes, but the scheduler thread pool does not perform any writes.
+When TiKV detects that the CPU core number of the machine is greater than or equal to `16`, this parameter value defaults to `8`. When the CPU core number is smaller than `16`, the parameter value defaults to `4`. This parameter is used when TiKV converts complex transaction requests to simple key-value reads or writes, but the scheduler thread pool does not performs any writes.
 
 Ideally, the usage rate of the scheduler thread pool is kept between 50% and 75%. Similar to the gRPC thread pool, the `storage.scheduler-worker-pool-size` parameter defaults to a larger value during the hybrid deployment, which makes resource usage insufficient. In this test, the value of this parameter is set to `2`, which is in line with the best practices, a conclusion drawn by observing the corresponding metrics in the **Scheduler worker CPU** panel.
 

br/backup-and-restore-storages.md

@@ -10,9 +10,9 @@ TiDB supports storing backup data to Amazon S3, Google Cloud Storage (GCS), Azur
 
 ## Send credentials to TiKV
 
-| CLI parameter                | Description                                                  | Default value |
-|:-----------------------------|:-------------------------------------------------------------|:--------------|
-| `--send-credentials-to-tikv` | Controls whether to send credentials obtained by BR to TiKV. | `true`        |
+| CLI parameter | Description | Default value
+|:----------|:-------|:-------|
+| `--send-credentials-to-tikv` | Controls whether to send credentials obtained by BR to TiKV. | `true`|
 
 By default, BR sends a credential to each TiKV node when using Amazon S3, GCS, or Azure Blob Storage as the storage system. This behavior simplifies the configuration and is controlled by the parameter `--send-credentials-to-tikv`(or `-c` in short).