information-schema: add tidb_hot_regions_history docs and update tidb_hot_regions

TOC.md

@@ -587,6 +587,7 @@
         - [`TABLE_CONSTRAINTS`](/information-schema/information-schema-table-constraints.md)
         - [`TABLE_STORAGE_STATS`](/information-schema/information-schema-table-storage-stats.md)
         - [`TIDB_HOT_REGIONS`](/information-schema/information-schema-tidb-hot-regions.md)
+        - [`TIDB_HOT_REGIONS_HISTORY`](/information-schema/information-schema-tidb-hot-regions-history.md)
         - [`TIDB_INDEXES`](/information-schema/information-schema-tidb-indexes.md)
         - [`TIDB_SERVERS_INFO`](/information-schema/information-schema-tidb-servers-info.md)
         - [`TIDB_TRX`](/information-schema/information-schema-tidb-trx.md)

information-schema/information-schema-tidb-hot-regions-history.md

@@ -0,0 +1,116 @@
+---
+title: TIDB_HOT_REGIONS_HISTORY
+summary: Learn the `TIDB_HOT_REGIONS_HISTORY` information_schema table.
+---
+
+# TIDB_HOT_REGIONS_HISTORY
+
+The `TIDB_HOT_REGIONS_HISTORY` table provides information about history hot regions that are periodically recorded locally by PD. You can specify the recorded interval by configuring [' hot-regions-write-interval '](/pd-configuration-file.md#hot-regions-write-interval). The default value is 10 minutes. You can specify the period for reserving history information about hot regions by configuring [' hot-regions-reserve-days'](/pd-configuration-file.md#hot-regions-write-interval). The default value is 7 days. See [PD configuration file description](/pd-configuration-file.md#hot-regions-write-interval) for details.
+
+{{< copyable "sql" >}}
+
+```sql
+USE information_schema;
+DESC tidb_hot_regions_history;
+```
+
+```sql
++-------------+--------------+------+------+---------+-------+
+| Field       | Type         | Null | Key  | Default | Extra |
++-------------+--------------+------+------+---------+-------+
+| UPDATE_TIME | timestamp(6) | YES  |      | NULL    |       |
+| DB_NAME     | varchar(64)  | YES  |      | NULL    |       |
+| TABLE_NAME  | varchar(64)  | YES  |      | NULL    |       |
+| TABLE_ID    | bigint(21)   | YES  |      | NULL    |       |
+| INDEX_NAME  | varchar(64)  | YES  |      | NULL    |       |
+| INDEX_ID    | bigint(21)   | YES  |      | NULL    |       |
+| REGION_ID   | bigint(21)   | YES  |      | NULL    |       |
+| STORE_ID    | bigint(21)   | YES  |      | NULL    |       |
+| PEER_ID     | bigint(21)   | YES  |      | NULL    |       |
+| IS_LEARNER  | tinyint(1)   | NO   |      | 0       |       |
+| IS_LEADER   | tinyint(1)   | NO   |      | 0       |       |
+| TYPE        | varchar(64)  | YES  |      | NULL    |       |
+| HOT_DEGREE  | bigint(21)   | YES  |      | NULL    |       |
+| FLOW_BYTES  | double       | YES  |      | NULL    |       |
+| KEY_RATE    | double       | YES  |      | NULL    |       |
+| QUERY_RATE  | double       | YES  |      | NULL    |       |
++-------------+--------------+------+------+---------+-------+
+16 rows in set (0.00 sec)
+```
+
+The fields in the `TIDB_HOT_REGIONS_HISTORY` table are described as follows:
+
+* UPDATE_TIME: Update time of the hot Region.
+* DB_NAME: The database name of the object in which the hot Region is located.
+* TABLE_ID: The ID of the table in which the hot Region is located.
+* TABLE_NAME: The name of the table in which the hot Region is located.
+* INDEX_NAME: The name of the index in which the hot Region is located.
+* INDEX_ID: The ID of the index in which the hot Region is located.
+* REGION_ID: The ID of the hot Region.
+* STORE_ID: The ID of the store in which the hot Region is located.
+* PEER_ID: The ID of the Peer corresponding to the hot Region.
+* IS_LEARNER: Whether the PEER is the LEARNER.
+* IS_LEADER: Whether the PEER is the LEADER.
+* TYPE: The type of the hot Region.
+* HOT_DEGREE: The hot degree of the hot Region.
+* FLOW_BYTES: The number of bytes written and read in the Region.
+* KEY_RATE: The number of keys written and read in the Region.
+* QUERY_RATE: The number of queries written and read in the Region.
+
+> **Note:**
+>
+> + `UPDATE_TIME`, `REGION_ID`, `STORE_ID`, `PEER_ID`, `IS_LEARNER`, `IS_LEADER` and `TYPE` fields are pushed down to the PD servers for execution. To reduce the overhead of using the table, you must specify the time range for the search, and specify as many conditions as possible. For example, `select * from tidb_hot_regions_history where store_id = 11 and update_time > '2020-05-18 20:40:00' and update_time < '2020-05-18 21:40:00' and type='write'`.
+
+The following are some scenarios:
+
+* Query hot Regions within a specific period of time. Replace update_time with your actual time.
+
+  {{< copyable "sql" >}}
+
+  ```sql
+  SELECT * FROM INFORMATION_SCHEMA.TIDB_HOT_REGIONS_HISTORY WHERE update_time >'2021-08-18 21:40:00' and update_time <'2021-09-19 00:00:00';
+  ```
+
+  > **Note:**
+  >
+  > + `UPDATE_TIME` also supports Unix timestamps. For example, `update_time >TIMESTAMP('2021-08-18 21:40:00')` or `update_time > FROM_UNIXTIME(1629294000.000)` .
+
+* Query hot Regions in a table within a specific period of time. Replace update_time and table_name with your actual values.
+
+  {{< copyable "sql" >}}
+
+  ```SQL
+  SELECT * FROM INFORMATION_SCHEMA.TIDB_HOT_REGIONS_HISTORY WHERE update_time >'2021-08-18 21:40:00' and update_time <'2021-09-19 00:00:00' and TABLE_NAME = 'table_name';
+  ```
+
+* Query the distribution of hot Regions within a specific period of time. Replace update_time and table_name with your actual values.
+
+  {{< copyable "sql" >}}
+
+  ```sql
+  SELECT count(region_id) cnt, store_id FROM INFORMATION_SCHEMA.TIDB_HOT_REGIONS_HISTORY WHERE update_time >'2021-08-18 21:40:00' and update_time <'2021-09-19 00:00:00' and table_name = 'table_name' GROUP BY STORE_ID ORDER BY cnt DESC;
+  ```
+
+* Query the distribution of hot Leader Regions within a specific period of time. Replace update_time and table_name with your actual values.
+
+  {{< copyable "sql" >}}
+
+  ```sql
+  SELECT count(region_id) cnt, store_id FROM INFORMATION_SCHEMA.TIDB_HOT_REGIONS_HISTORY WHERE update_time >'2021-08-18 21:40:00' and update_time <'2021-09-19 00:00:00' and table_name = 'table_name' and is_leader=1 GROUP BY STORE_ID ORDER BY cnt DESC;
+  ```
+
+* Query the distribution of hot Index Regions within a specific period of time. Replace update_time and table_name with your actual values.
+
+  {{< copyable "sql" >}}
+
+  ```sql
+  SELECT count(region_id) cnt, index_name, store_id FROM INFORMATION_SCHEMA.TIDB_HOT_REGIONS_HISTORY WHERE update_time >'2021-08-18 21:40:00' and update_time <'2021-09-19 00:00:00' and table_name = 'table_name' group by index_name, store_id order by index_name,cnt desc;
+  ```
+
+* Query the distribution of hot Index Leader Regions within a specific period of time. Replace update_time and table_name with your actual values.
+
+  {{< copyable "sql" >}}
+
+  ```sql
+  SELECT count(region_id) cnt, index_name, store_id FROM INFORMATION_SCHEMA.TIDB_HOT_REGIONS_HISTORY WHERE update_time >'2021-08-18 21:40:00' and update_time <'2022-09-19 00:00:00' and table_name = 'table_name' and is_leader=1 group by index_name, store_id order by index_name,cnt desc;
+  ```

information-schema/information-schema-tidb-hot-regions.md

@@ -5,7 +5,7 @@ summary: Learn the `TIDB_HOT_REGIONS` information_schema table.
 
 # TIDB_HOT_REGIONS
 
-The `TIDB_HOT_REGIONS` table provides information about hotspot Regions.
+The `TIDB_HOT_REGIONS` table provides information about the current hot Regions. For information about history hot regions, see `[TIDB_HOT_REGIONS_HISTORY](/information-schema/information-schema-tidb-hot-regions-history.md)`.
 
 {{< copyable "sql" >}}
 
@@ -34,13 +34,13 @@ DESC tidb_hot_regions;
 
 The description of columns in the `TIDB_HOT_REGIONS` table is as follows:
 
-* `TABLE_ID`: ID of located.
-* `INDEX_ID`: ID of the table in which the hot Region is the index in which the hot Region is located.
+* `TABLE_ID`: The ID of the table in which the hot Region is located.
+* `INDEX_ID`: The ID of the index in which the hot Region is located.
 * `DB_NAME`: The database name of the object in which the hot Region is located.
 * `TABLE_NAME`: The name of the table in which the hot Region is located.
 * `INDEX_NAME`: The name of the index in which the hot Region is located.
-* `REGION_ID`: ID of the hot Region.
+* `REGION_ID`: The ID of the hot Region.
 * `TYPE`: The type of the hot Region.
 * `MAX_HOT_DEGREE`: The maximum hot degree of the Region.
-* `REGION_COUNT`: The number of Regions in the instance. 
+* `REGION_COUNT`: The number of hot Regions in the instance. 
 * `FLOW_BYTES`: The number of bytes written and read in the Region.

information-schema/information-schema.md

@@ -83,6 +83,7 @@ Many `INFORMATION_SCHEMA` tables have a corresponding `SHOW` command. The benefi
 | [`STATEMENTS_SUMMARY_HISTORY`](/statement-summary-tables.md)                            | Similar to performance_schema statement summary history in MySQL. |
 | [`TABLE_STORAGE_STATS`](/information-schema/information-schema-table-storage-stats.md)  | Provides details about table sizes in storage. |
 | [`TIDB_HOT_REGIONS`](/information-schema/information-schema-tidb-hot-regions.md)        | Provides statistics about which regions are hot. |
+| [`TIDB_HOT_REGIONS_HISTORY`](/information-schema/information-schema-tidb-hot-regions-history.md) | Provides history statistics about which regions are hot. |
 | [`TIDB_INDEXES`](/information-schema/information-schema-tidb-indexes.md)                | Provides index information about TiDB tables. |
 | [`TIDB_SERVERS_INFO`](/information-schema/information-schema-tidb-servers-info.md)      | Provides a list of TiDB servers (namely, tidb-server component) |
 | [`TIDB_TRX`](/information-schema/information-schema-tidb-trx.md) | Provides the information of the transactions that are being executed on the TiDB node. |