update

Signed-off-by: nolouch <[email protected]>
pingcap · Jan 15, 2025 · ef39b08 · ef39b08
1 parent 7374391
commit ef39b08
Show file tree

Hide file tree

Showing 6 changed files with 13 additions and 13 deletions.
diff --git a/information-schema/information-schema-resource-groups.md b/information-schema/information-schema-resource-groups.md
@@ -5,7 +5,7 @@ summary: Learn the `RESOURCE_GROUPS` information_schema table.
 
 # RESOURCE_GROUPS
 
-The `RESOURCE_GROUPS` table shows the information about all resource groups. For more information, see [Use Resource Control to Achieve Resource Isolation](/tidb-resource-control.md).
+The `RESOURCE_GROUPS` table shows the information about all resource groups. For more information, see [Use Resource Control to Achieve resource group limitation](/tidb-resource-control.md).
 
 > **Note:**
 >

diff --git a/releases/release-8.4.0.md b/releases/release-8.4.0.md
@@ -156,7 +156,7 @@ Quick access: [Quick start](https://docs.pingcap.com/tidb/v8.4/quick-start-with-
 
     Starting from TiDB v8.4.0, you can switch the resource group of runaway queries to a specific one. If the `COOLDOWN` mechanism fails to lower resource consumption, you can create a [resource group](/tidb-resource-control.md#create-a-resource-group), limit its resource size, and set the `SWITCH_GROUP` parameter to move identified runaway queries to this group. Meanwhile, subsequent queries within the same session will continue to execute in the original resource group. By switching resource groups, you can manage resource usage more precisely, and control the resource consumption more strictly.
 
-    For more information, see [documentation](/tidb-resource-control.md#query_limit-parameters).
+    For more information, see [documentation](/tidb-resource-control-runaway-queries.md#query_limit-parameters).
 
 * Support setting the cluster-level Region scattering strategy using the `tidb_scatter_region` system variable [#55184](https://github.com/pingcap/tidb/issues/55184) @[D3Hunter](https://github.com/D3Hunter)
 

diff --git a/system-variable-reference.md b/system-variable-reference.md
@@ -1895,7 +1895,7 @@ Referenced in:
 - [SET RESOURCE GROUP](/sql-statements/sql-statement-set-resource-group.md)
 - [System Variables](/system-variables.md#tidb_enable_resource_control-new-in-v660)
 - [TiKV Configuration File](/tikv-configuration-file.md)
-- [Use Resource Control to Achieve Resource Isolation](/tidb-resource-control.md)
+- [Use Resource Control to Achieve resource group limitation](/tidb-resource-control.md)
 - [`CALIBRATE RESOURCE`](/sql-statements/sql-statement-calibrate-resource.md)
 - [TiDB 7.4.0 Release Notes](/releases/release-7.4.0.md)
 - [TiDB 7.0.0 Release Notes](/releases/release-7.0.0.md)
@@ -2479,7 +2479,7 @@ Referenced in:
 Referenced in:
 
 - [System Variables](/system-variables.md#tidb_last_query_info-new-in-v4014)
-- [Use Resource Control to Achieve Resource Isolation](/tidb-resource-control.md)
+- [Use Resource Control to Achieve resource group limitation](/tidb-resource-control.md)
 - [TiDB 7.6.0 Release Notes](/releases/release-7.6.0.md)
 - [TiDB 7.5.1 Release Notes](/releases/release-7.5.1.md)
 
@@ -3353,7 +3353,7 @@ Referenced in:
 Referenced in:
 
 - [System Variables](/system-variables.md#tidb_request_source_type-new-in-v740)
-- [Use Resource Control to Achieve Resource Isolation](/tidb-resource-control.md)
+- [Use Resource Control to Achieve resource group limitation](/tidb-resource-control.md)
 - [TiDB 7.4.0 Release Notes](/releases/release-7.4.0.md)
 
 ### tidb_resource_control_strict_mode
@@ -3364,7 +3364,7 @@ Referenced in:
 - [Privilege Management](/privilege-management.md)
 - [SET RESOURCE GROUP](/sql-statements/sql-statement-set-resource-group.md)
 - [System Variables](/system-variables.md#tidb_resource_control_strict_mode-new-in-v820)
-- [Use Resource Control to Achieve Resource Isolation](/tidb-resource-control.md)
+- [Use Resource Control to Achieve resource group limitation](/tidb-resource-control.md)
 - [TiDB 8.2.0 Release Notes](/releases/release-8.2.0.md)
 
 ### tidb_restricted_read_only
@@ -4152,7 +4152,7 @@ Referenced in:
 - [Limited SQL features on TiDB Cloud](https://docs.pingcap.com/tidbcloud/limited-sql-features)
 - [System Variables](/system-variables.md#txn_scope)
 - [TiDB Configuration File](/tidb-configuration-file.md)
-- [Use Resource Control to Achieve Resource Isolation](/tidb-resource-control.md)
+- [Use Resource Control to Achieve resource group limitation](/tidb-resource-control.md)
 
 ### validate_password.check_user_name
 

diff --git a/tidb-resource-control-runaway-queries.md b/tidb-resource-control-runaway-queries.md
@@ -5,7 +5,7 @@ summary: Introduces how to control and degrade queries with excessive resource c
 
 # Manage queries that consume more resources than expected (Runaway Queries)
 
-A runaway query is a query (`SELECT` statement only) that consumes more time or resources than expected. The term **runaway queries** is used in the following to describe the feature of managing the runaway query.
+A runaway query is a query that consumes more time or resources than expected. The term **runaway queries** is used in the following to describe the feature of managing the runaway query.
 
 - Starting from v7.2.0, the resource control feature introduces the management of runaway queries. You can set criteria for a resource group to identify runaway queries and automatically take actions to prevent them from exhausting resources and affecting other queries. You can manage runaway queries for a resource group by including the `QUERY_LIMIT` field in [`CREATE RESOURCE GROUP`](/sql-statements/sql-statement-create-resource-group.md) or [`ALTER RESOURCE GROUP`](/sql-statements/sql-statement-alter-resource-group.md).
 - Starting from v7.3.0, the resource control feature introduces manual management of runaway watches, enabling quick identification of runaway queries for a given SQL statement or Digest. You can execute the statement [`QUERY WATCH`](/sql-statements/sql-statement-query-watch.md) to manually manage the runaway queries watch list in the resource group.
@@ -14,9 +14,9 @@ A runaway query is a query (`SELECT` statement only) that consumes more time or
 
 If a query exceeds any of the following limits, it is identified as a runaway query:
 
-- `EXEC_ELAPSED`: checks whether the query execution time exceeds the limit.
-- `PROCESSED_KEYS`: checks whether the number of keys processed by the Coprocessor exceeds the limit.
-- `RU`: checks whether the total number of read and write RUs consumed by the statement exceeds the limit.
+- `EXEC_ELAPSED`: checks whether the query execution time exceeds the limit, this rule applies to read and write DML.
+- `PROCESSED_KEYS`: checks whether the number of keys processed by the Coprocessor exceeds the limit, this rule applies only to read statements.
+- `RU`: checks whether the total number of read and write RUs consumed by the statement exceeds the limit, this rule applies only to read statements.
 
 Supported operations (`ACTION`):
 

diff --git a/tiflash/tiflash-pipeline-model.md b/tiflash/tiflash-pipeline-model.md
@@ -10,7 +10,7 @@ This document introduces the TiFlash pipeline execution model.
 Starting from v7.2.0, TiFlash supports a new execution model, the pipeline execution model.
 
 - For v7.2.0 and v7.3.0: The pipeline execution model is experimental and is controlled by [`tidb_enable_tiflash_pipeline_model`](https://docs.pingcap.com/tidb/v7.2/system-variables#tidb_enable_tiflash_pipeline_model-introduced-since-v720).
-- For v7.4.0 and later versions: The pipeline execution model becomes generally available. It is an internal feature of TiFlash and is tightly integrated with TiFlash resource control. When you enable TiFlash resource control, the pipeline execution model is automatically enabled. For more information about how to use TiFlash resource control, refer to [Use resource control to achieve resource isolation](/tidb-resource-control.md#parameters-for-resource-control). Additionally, starting from v7.4.0, the system variable `tidb_enable_tiflash_pipeline_model` is deprecated.
+- For v7.4.0 and later versions: The pipeline execution model becomes generally available. It is an internal feature of TiFlash and is tightly integrated with TiFlash resource control. When you enable TiFlash resource control, the pipeline execution model is automatically enabled. For more information about how to use TiFlash resource control, refer to [Use Resource Control to Achieve resource group limitation](/tidb-resource-control.md#parameters-for-resource-control). Additionally, starting from v7.4.0, the system variable `tidb_enable_tiflash_pipeline_model` is deprecated.
 
 Inspired by the paper [Morsel-Driven Parallelism: A NUMA-Aware Query Evaluation Framework for the Many-Core Age](https://dl.acm.org/doi/10.1145/2588555.2610507), the TiFlash pipeline execution model provides a fine-grained task scheduling model, which is different from the traditional thread scheduling model. It reduces the overhead of operating system thread application and scheduling and provides a fine-grained scheduling mechanism.
 

diff --git a/user-account-management.md b/user-account-management.md
@@ -146,7 +146,7 @@ TiDB creates the `'root'@'%'` default account during the database initialization
 
 ## Set account resource limits
 
-TiDB can limit the resources consumed by users using resource groups. For more information, see [Use resource control to achieve resource isolation](/tidb-resource-control.md).
+TiDB can limit the resources consumed by users using resource groups. For more information, see [Use Resource Control to Achieve resource group limitation](/tidb-resource-control.md).
 
 ## Assign account passwords