Statistics are not match with PD when querying INFORMATION_SCHEMA.TIDB_HOT_REGIONS

[rleungx]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Analyze a table, and use select * from INFORMATION_SCHEMA.TIDB_HOT_REGIONS.

2. What did you expect to see? (Required)

The hot regions' statistics

3. What did you see instead (Required)

Use SQL:

Directly use pd-ctl hot read:

» hot read
{
  ...
  "as_leader": {
    "1": {
      ...
      "statistics": [
        {
          "store_id": 1,
          "region_id": 25885,
          "hot_degree": 3,
          ...
          "flow_bytes": 120523.79999999999,
          "flow_keys": 493.95,
          ...
        }
      ]
    },
    "116": {
      ...
      "statistics": [
        {
          "store_id": 116,
          "region_id": 55531,
          "hot_degree": 8,
          ...
          "flow_bytes": 39862.28333333333,
          "flow_keys": 6.491666666666666,
          ...
        }
      ]
    },
    "88": {
      ...
      "statistics": [
        {
          "store_id": 88,
          "region_id": 25947,
          "hot_degree": 3,
          ...
          "flow_bytes": 123419.26666666666,
          "flow_keys": 505.8166666666667,
          ...
        }
      ]
    }
  }
}

4. What is your TiDB version? (Required)

Release Version: v4.0.8
Edition: Community
Git Commit Hash: 66ac9fc31f1733e5eb8d11891ec1b38f9c422817
Git Branch: heads/refs/tags/v4.0.8
UTC Build Time: 2020-10-30 08:21:16
GoVersion: go1.13
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false

[ti-srebot]

Please edit this comment or add a new comment to complete the following information

Not a bug

1. Remove the 'type/bug' label
2. Add notes to indicate why it is not a bug

Duplicate bug

1. Add the 'type/duplicate' label
2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions