sql-infra: add resource control feature

TOC.md

@@ -159,6 +159,7 @@
       - [Back up and Restore Data Using Dumpling and TiDB Lightning](/backup-and-restore-using-dumpling-lightning.md)
       - [Back Up and Restore RawKV](/br/rawkv-backup-and-restore.md)
       - [Incremental Backup and Restore](/br/br-incremental-guide.md)
+  - [Resource Control](/tidb-resource-control.md)
   - [Configure Time Zone](/configure-time-zone.md)
   - [Daily Checklist](/daily-check.md)
   - [Maintain TiFlash](/tiflash/maintain-tiflash.md)
@@ -606,6 +607,7 @@
     - [TiKV](/grafana-tikv-dashboard.md)
     - [TiFlash](/tiflash/monitor-tiflash.md)
     - [TiCDC](/ticdc/monitor-ticdc.md)
+    - [Resource Control](/grafana-resource-control-dashboard.md)
   - Secure
     - [Enable TLS Between TiDB Clients and Servers](/enable-tls-between-clients-and-servers.md)
     - [Enable TLS Between TiDB Components](/enable-tls-between-components.md)
@@ -645,6 +647,7 @@
       - [`ALTER INDEX`](/sql-statements/sql-statement-alter-index.md)
       - [`ALTER INSTANCE`](/sql-statements/sql-statement-alter-instance.md)
       - [`ALTER PLACEMENT POLICY`](/sql-statements/sql-statement-alter-placement-policy.md)
+      - [`ALTER RESOURCE GROUP`](/sql-statements/sql-statement-alter-resource-group.md)
       - [`ALTER TABLE`](/sql-statements/sql-statement-alter-table.md)
       - [`ALTER TABLE COMPACT`](/sql-statements/sql-statement-alter-table-compact.md)
       - [`ALTER USER`](/sql-statements/sql-statement-alter-user.md)
@@ -660,6 +663,7 @@
       - [`CREATE DATABASE`](/sql-statements/sql-statement-create-database.md)
       - [`CREATE INDEX`](/sql-statements/sql-statement-create-index.md)
       - [`CREATE PLACEMENT POLICY`](/sql-statements/sql-statement-create-placement-policy.md)
+      - [`CREATE RESOURCE GROUP`](/sql-statements/sql-statement-create-resource-group.md)
       - [`CREATE ROLE`](/sql-statements/sql-statement-create-role.md)
       - [`CREATE SEQUENCE`](/sql-statements/sql-statement-create-sequence.md)
       - [`CREATE TABLE LIKE`](/sql-statements/sql-statement-create-table-like.md)
@@ -676,6 +680,7 @@
       - [`DROP DATABASE`](/sql-statements/sql-statement-drop-database.md)
       - [`DROP INDEX`](/sql-statements/sql-statement-drop-index.md)
       - [`DROP PLACEMENT POLICY`](/sql-statements/sql-statement-drop-placement-policy.md)
+      - [`DROP RESOURCE GROUP`](/sql-statements/sql-statement-drop-resource-group.md)
       - [`DROP ROLE`](/sql-statements/sql-statement-drop-role.md)
       - [`DROP SEQUENCE`](/sql-statements/sql-statement-drop-sequence.md)
       - [`DROP STATS`](/sql-statements/sql-statement-drop-stats.md)
@@ -727,6 +732,7 @@
       - [`SHOW CONFIG`](/sql-statements/sql-statement-show-config.md)
       - [`SHOW CREATE DATABASE`](/sql-statements/sql-statement-show-create-database.md)
       - [`SHOW CREATE PLACEMENT POLICY`](/sql-statements/sql-statement-show-create-placement-policy.md)
+      - [`SHOW CREATE RESOURCE GROUP`](/sql-statements/sql-statement-show-create-resource-group.md)
       - [`SHOW CREATE SEQUENCE`](/sql-statements/sql-statement-show-create-sequence.md)
       - [`SHOW CREATE TABLE`](/sql-statements/sql-statement-show-create-table.md)
       - [`SHOW CREATE USER`](/sql-statements/sql-statement-show-create-user.md)
@@ -852,6 +858,7 @@
         - [`PLACEMENT_POLICIES`](/information-schema/information-schema-placement-policies.md)
         - [`PROCESSLIST`](/information-schema/information-schema-processlist.md)
         - [`REFERENTIAL_CONSTRAINTS`](/information-schema/information-schema-referential-constraints.md)
+        - [`RESOURCE_GROUPS`](/information-schema/information-schema-resource-groups.md)
         - [`SCHEMATA`](/information-schema/information-schema-schemata.md)
         - [`SEQUENCES`](/information-schema/information-schema-sequences.md)
         - [`SESSION_VARIABLES`](/information-schema/information-schema-session-variables.md)

grafana-resource-control-dashboard.md

@@ -0,0 +1,36 @@
+---
+title: Key Monitoring Metrics of Resource Control
+summary: Learn some key metrics displayed on the Grafana Resource Control dashboard.
+---
+
+# Key Monitoring Metrics of Resource Control
+
+If you use TiUP to deploy the TiDB cluster, the monitoring system (Prometheus & Grafana) is deployed at the same time. For more information, see [Overview of the Monitoring Framework](/tidb-monitoring-framework.md).
+
+The Grafana dashboard is divided into a series of sub dashboards which include Overview, PD, TiDB, TiKV, Node\_exporter, Disk Performance, and Performance\_overview. A lot of metrics are there to help you diagnose.
+
+You can get an overview of the resource control status from the PD dashboard, where the key metrics are displayed. This document provides a detailed description of these key metrics.
+
+This document describes some key monitoring metrics displayed on the Resource Control Dashboard.
+
+## Metrics about Request Unit
+
+- RU: the [Request Unit (RU)](/tidb-resource-control.md#what-is-request-unit-ru) consumption information of each resource group is calculated in real time. `total` is the sum of the Request Units consumed by all Resource Groups. The Request Unit consumption of each resource group should be equal to the sum of its read consumption (Read Request Unit) and write consumption (Write Request Unit).
+- RU Per Query: the average number of Request Units consumed by each SQL statement per second. It is obtained by dividing the above Request Unit by the number of SQL statements executed per second.
+- RRU: the Read Request Unit consumption information of each resource group is calculated in real time. `total` is the sum of the Read Request Units consumed by all Resource Groups.
+- RRU Per Query: the average number of Read Request Units consumed by each SQL statement per second. It is obtained by dividing the above Read Request Unit by the number of SQL statements executed per second.
+- WRU: the Write Request Unit consumption information of each resource group is calculated in real time. `total` is the sum of the Write Request Units consumed by all Resource Groups.
+- WRU Per Query: the average number of Write Request Units consumed by each SQL statement per second. It is obtained by dividing the above Write Request Unit by the number of SQL statements executed per second.
+
+## Metrics about resources
+
+- KV Request Count: the number of KV requests is calculated in real time for each resource group. They are divided into read and write types. `total` is the sum of the KV requests involved by all Resource Groups.
+- KV Request Count Per Query: the average number of read and write KV requests by each SQL statement per second. It is obtained by dividing the above KV Request Count by the number of SQL statements executed per second.
+- Bytes Read: the amount of data read is calculated in real time for each resource group. `total` is the sum of the data read by all Resource Groups.
+- Bytes Read Per Query: the average amount of data read by each SQL statement per second. It is obtained by dividing the above Bytes Read by the number of SQL statements executed per second.
+- Bytes Written: the amount of data written is calculated in real time for each resource group. `total` is the sum of the data written by all Resource Groups.
+- Bytes Written Per Query: the average amount of data written by each SQL statement per second. It is obtained by dividing the above Bytes Written by the number of SQL statements executed per second.
+- KV CPU Time: the KV layer CPU time consumed is calculated in real time for each resource group. `total` is the sum of the KV layer CPU time consumed by all Resource Groups.
+- KV CPU Time Per Query: the average KV layer CPU time consumed by each SQL statement per second. It is obtained by dividing the above KV CPU Time by the number of SQL statements executed per second.
+- SQL CPU Time: the SQL layer CPU time consumed is calculated in real time for each resource group. `total` is the sum of the SQL layer CPU time consumed by all Resource Groups.
+- SQL CPU Time Per Query: the average SQL layer CPU time consumed by each SQL statement per second. It is obtained by dividing the above SQL CPU Time by the number of SQL statements executed per second.

information-schema/information-schema-processlist.md

@@ -12,7 +12,8 @@ The `PROCESSLIST` table has additional columns not present in `SHOW PROCESSLIST`
 * A `DIGEST` column to show the digest of the SQL statement.
 * A `MEM` column to show the memory used by the request that is being processed, in bytes.
 * A `DISK` column to show the disk usage in bytes.
-* A `TxnStart` column to show the start time of the transaction
+* A `TxnStart` column to show the start time of the transaction.
+* A `RESOURCE_GROUP` column to show the resource group name.
 
 {{< copyable "sql" >}}
 
@@ -21,44 +22,47 @@ USE information_schema;
 DESC processlist;
 ```
 
-```
-+----------+---------------------+------+------+---------+-------+
-| Field    | Type                | Null | Key  | Default | Extra |
-+----------+---------------------+------+------+---------+-------+
-| ID       | bigint(21) unsigned | NO   |      | 0       |       |
-| USER     | varchar(16)         | NO   |      |         |       |
-| HOST     | varchar(64)         | NO   |      |         |       |
-| DB       | varchar(64)         | YES  |      | NULL    |       |
-| COMMAND  | varchar(16)         | NO   |      |         |       |
-| TIME     | int(7)              | NO   |      | 0       |       |
-| STATE    | varchar(7)          | YES  |      | NULL    |       |
-| INFO     | longtext            | YES  |      | NULL    |       |
-| DIGEST   | varchar(64)         | YES  |      |         |       |
-| MEM      | bigint(21) unsigned | YES  |      | NULL    |       |
-| DISK     | bigint(21) unsigned | YES  |      | NULL    |       |
-| TxnStart | varchar(64)         | NO   |      |         |       |
-+----------+---------------------+------+------+---------+-------+
-12 rows in set (0.00 sec)
+```sql
++---------------------+---------------------+------+------+---------+-------+
+| Field               | Type                | Null | Key  | Default | Extra |
++---------------------+---------------------+------+------+---------+-------+
+| ID                  | bigint(21) unsigned | NO   |      | 0       |       |
+| USER                | varchar(16)         | NO   |      |         |       |
+| HOST                | varchar(64)         | NO   |      |         |       |
+| DB                  | varchar(64)         | YES  |      | NULL    |       |
+| COMMAND             | varchar(16)         | NO   |      |         |       |
+| TIME                | int(7)              | NO   |      | 0       |       |
+| STATE               | varchar(7)          | YES  |      | NULL    |       |
+| INFO                | longtext            | YES  |      | NULL    |       |
+| DIGEST              | varchar(64)         | YES  |      |         |       |
+| MEM                 | bigint(21) unsigned | YES  |      | NULL    |       |
+| DISK                | bigint(21) unsigned | YES  |      | NULL    |       |
+| TxnStart            | varchar(64)         | NO   |      |         |       |
+| RESOURCE_GROUP      | varchar(32)         | NO   |      |         |       |
++---------------------+---------------------+------+------+---------+-------+
+13 rows in set (0.00 sec)
 ```
 
 {{< copyable "sql" >}}
 
 ```sql
 SELECT * FROM processlist\G
 ```
-
-```
+```sql
 *************************** 1. row ***************************
-      ID: 16
-    USER: root
-    HOST: 127.0.0.1
-      DB: information_schema
- COMMAND: Query
-    TIME: 0
-   STATE: autocommit
-    INFO: SELECT * FROM processlist
-     MEM: 0
-TxnStart:
+                 ID: 2300033189772525975
+               USER: root
+               HOST: 127.0.0.1:51289
+                 DB: NULL
+            COMMAND: Query
+               TIME: 0
+              STATE: autocommit
+               INFO: SELECT * FROM processlist
+             DIGEST: dbfaa16980ec628011029f0aaf0d160f4b040885240dfc567bf760d96d374f7e
+                MEM: 0
+               DISK: 0
+           TxnStart:
+     RESOURCE_GROUP: rg1
 1 row in set (0.00 sec)
 ```
 
@@ -76,6 +80,7 @@ Fields in the `PROCESSLIST` table are described as follows:
 * MEM: The memory used by the request that is being processed, in bytes.
 * DISK: The disk usage in bytes.
 * TxnStart: The start time of the transaction.
+* RESOURCE_GROUP: The resource group name.
 
 ## CLUSTER_PROCESSLIST
 
@@ -88,13 +93,14 @@ SELECT * FROM information_schema.cluster_processlist;
 ```
 
 ```sql
-+-----------------+-----+------+----------+------+---------+------+------------+------------------------------------------------------+-----+----------------------------------------+
-| INSTANCE        | ID  | USER | HOST     | DB   | COMMAND | TIME | STATE      | INFO                                                 | MEM | TxnStart                               |
-+-----------------+-----+------+----------+------+---------+------+------------+------------------------------------------------------+-----+----------------------------------------+
-| 10.0.1.22:10080 | 150 | u1   | 10.0.1.1 | test | Query   | 0    | autocommit | select count(*) from usertable                       | 372 | 05-28 03:54:21.230(416976223923077223) |
-| 10.0.1.22:10080 | 138 | root | 10.0.1.1 | test | Query   | 0    | autocommit | SELECT * FROM information_schema.cluster_processlist | 0   | 05-28 03:54:21.230(416976223923077220) |
-| 10.0.1.22:10080 | 151 | u1   | 10.0.1.1 | test | Query   | 0    | autocommit | select count(*) from usertable                       | 372 | 05-28 03:54:21.230(416976223923077224) |
-| 10.0.1.21:10080 | 15  | u2   | 10.0.1.1 | test | Query   | 0    | autocommit | select max(field0) from usertable                    | 496 | 05-28 03:54:21.230(416976223923077222) |
-| 10.0.1.21:10080 | 14  | u2   | 10.0.1.1 | test | Query   | 0    | autocommit | select max(field0) from usertable                    | 496 | 05-28 03:54:21.230(416976223923077225) |
-+-----------------+-----+------+----------+------+---------+------+------------+------------------------------------------------------+-----+----------------------------------------+
++-----------------+-----+------+----------+------+---------+------+------------+------------------------------------------------------+-----+----------------------------------------+----------------+
+| INSTANCE        | ID  | USER | HOST     | DB   | COMMAND | TIME | STATE      | INFO                                                 | MEM | TxnStart                               | RESOURCE_GROUP | 
++-----------------+-----+------+----------+------+---------+------+------------+------------------------------------------------------+-----+----------------------------------------+----------------+
+
+| 10.0.1.22:10080 | 150 | u1   | 10.0.1.1 | test | Query   | 0    | autocommit | select count(*) from usertable                       | 372 | 05-28 03:54:21.230(416976223923077223) | default        |
+| 10.0.1.22:10080 | 138 | root | 10.0.1.1 | test | Query   | 0    | autocommit | SELECT * FROM information_schema.cluster_processlist | 0   | 05-28 03:54:21.230(416976223923077220) | rg1            |
+| 10.0.1.22:10080 | 151 | u1   | 10.0.1.1 | test | Query   | 0    | autocommit | select count(*) from usertable                       | 372 | 05-28 03:54:21.230(416976223923077224) | rg2            |
+| 10.0.1.21:10080 | 15  | u2   | 10.0.1.1 | test | Query   | 0    | autocommit | select max(field0) from usertable                    | 496 | 05-28 03:54:21.230(416976223923077222) | default        |
+| 10.0.1.21:10080 | 14  | u2   | 10.0.1.1 | test | Query   | 0    | autocommit | select max(field0) from usertable                    | 496 | 05-28 03:54:21.230(416976223923077225) | default        |
++-----------------+-----+------+----------+------+---------+------+------------+------------------------------------------------------+-----+----------------------------------------+----------------+
 ```

information-schema/information-schema-resource-groups.md

@@ -0,0 +1,56 @@
+---
+title: RESOURCE_GROUPS
+summary: Learn the `RESOURCE_GROUPS` information_schema table.
+---
+
+# RESOURCE_GROUPS
+
+> **Warning:**
+>
+> This feature is experimental and its form and usage may change in subsequent versions.
+
+The `RESOURCE_GROUPS` table shows information about all resource groups. See [Use Resource Control to Achieve Resource Isolation](/tidb-resource-control.md).
+
+```sql
+USE information_schema;
+DESC resource_groups;
+```
+
+```sql
++------------+-------------+------+------+---------+-------+
+| Field      | Type        | Null | Key  | Default | Extra |
++------------+-------------+------+------+---------+-------+
+| NAME       | varchar(32) | NO   |      | NULL    |       |
+| RU_PER_SEC | bigint(21)  | YES  |      | NULL    |       |
+| BURSTABLE  | varchar(3)  | YES  |      | NULL    |       |
++------------+-------------+------+------+---------+-------+
+4 rows in set (0.00 sec)
+```
+
+## Examples
+
+{{< copyable "sql" >}}
+
+```sql
+mysql> CREATE RESOURCE GROUP rg1 RU_PER_SEC=1000; -- Create the resource group rg1
+Query OK, 0 rows affected (0.34 sec)
+mysql> SHOW CREATE RESOURCE GROUP rg1; -- Displays the definition of the rg1 resource group.
++----------------+---------------------------------------------+
+| Resource_Group | Create Resource Group                       |
++----------------+---------------------------------------------+
+| rg1            | CREATE RESOURCE GROUP `rg1` RU_PER_SEC=1000 |
++----------------+---------------------------------------------+
+1 row in set (0.00 sec)
+mysql> SELECT * FROM information_schema.resource_groups WHERE NAME = 'rg1';
++------+------------+-----------+
+| NAME | RU_PER_SEC | BURSTABLE |
++------+------------+-----------+
+| rg1  |       1000 | NO        |
++------+------------+-----------+
+```
+
+The descriptions of the columns in the `RESOURCE_GROUPS` table are as follows:
+
+* `NAME`: the name of the resource group.
+* `RU_PER_SEC`：the backfilling speed of the resource group. The unit is RU/second, in which RU means [Request Unit](/tidb-resource-control.md#what-is-request-unit-ru).
+* `BURSTABLE`: whether to allow the resource group to overuse the available system resources.

mysql-compatibility.md

@@ -260,3 +260,11 @@ TiDB does not implement certain features that have been marked as deprecated in
 
 * Specifying precision for floating point types. MySQL 8.0 [deprecates](https://dev.mysql.com/doc/refman/8.0/en/floating-point-types.html) this feature, and it is recommended to use the `DECIMAL` type instead.
 * The `ZEROFILL` attribute. MySQL 8.0 [deprecates](https://dev.mysql.com/doc/refman/8.0/en/numeric-type-attributes.html) this feature, and it is recommended to instead pad numeric values in your application.
+
+### `CREATE RESOURCE GROUP`, `DROP RESOURCE GROUP`, and `ALTER RESOURCE GROUP` statements
+
+The statements of creating and modifying resource groups are different from MySQL. See the following documents for details:
+
+- [`CREATE RESOURCE GROUP`](/sql-statements/sql-statement-create-resource-group.md)
+- [`DROP RESOURCE GROUP`](/sql-statements/sql-statement-drop-resource-group.md)
+- [`ALTER RESOURCE GROUP`](/sql-statements/sql-statement-alter-resource-group.md)

privilege-management.md

@@ -364,6 +364,18 @@ Requires `SUPER` privilege.
 
 Requires `SUPER` or `CONNECTION_ADMIN` privilege to kill other user sessions.
 
+### CREATE RESOURCE GROUP
+
+Requires `SUPER` or `RESOURCE_GROUP_ADMIN` privilege.
+
+### ALTER RESOURCE GROUP
+
+Requires `SUPER` or `RESOURCE_GROUP_ADMIN` privilege.
+
+### DROP RESOURCE GROUP
+
+Requires `SUPER` or `RESOURCE_GROUP_ADMIN` privilege.
+
 ## Implementation of the privilege system
 
 ### Privilege table