The STATUS field data in the TIKV_REGION_PEERS table is incorrect

[HunDunDM]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

• Randomly choose a Region containing down-peer (shutdown a TiKV in the cluster and wait for a while)
• pd-ctl region ${region_id}
• SELECT * FROM INFORMATION_SCHEMA.TIKV_REGION_PEERS WHERE REGION_ID=${region_id};

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

• Their data should be consistent.

3. What did you see instead (Required)

• Peer 691 is down but not in the SQL results.

region 689
Starting component `ctl`: /home/ubuntu/.tiup/components/ctl/v5.0.1/ctl pd -u http://10.0.1.165:2379 region 689
{
  "id": 689,
  "start_key": "7480000000000000FF335F728000000002FF64A9040000000000FA",
  "end_key": "7480000000000000FF335F728000000002FF73E6700000000000FA",
  "epoch": {
    "conf_ver": 47,
    "version": 61
  },
  "peers": [
    {
      "id": 690,
      "store_id": 100
    },
    {
      "id": 691,
      "store_id": 102
    },
    {
      "id": 692,
      "store_id": 101
    }
  ],
  "leader": {
    "id": 690,
    "store_id": 100
  },
  "down_peers": [
    {
      "peer": {
        "id": 691,
        "store_id": 102
      },
      "down_seconds": 306
    }
  ],
  "written_bytes": 0,
  "read_bytes": 0,
  "written_keys": 0,
  "read_keys": 0,
  "approximate_size": 49,
  "approximate_keys": 966592
}

> select region_id, status, store_id, store_state_name from tikv_region_peers join tikv_store_status using (store_id) where region_id=689;
+-----------+--------+----------+------------------+
| region_id | status | store_id | store_state_name |
+-----------+--------+----------+------------------+
|       689 | NORMAL |      100 | Up               |
|       689 | NORMAL |      102 | Offline          |
|       689 | NORMAL |      101 | Up               |
+-----------+--------+----------+------------------+

4. What is your TiDB version? (Required)

• v5.0.1

[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