Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 从5.1.1原地升级到6.1.1后bug-11217未解决
|
username: army
To improve efficiency, please provide the following information. A clear problem description can help solve the issue faster:
【TiDB Usage Environment】
5.7.25-TiDB-v6.1.1 TiDB Server (Apache License 2.0) Community Edition, MySQL 5.7 compatible
【Overview】 Scenario + Problem Overview
【Background】 Operations performed
analyze table test
【Phenomenon】 Business and database phenomena
【Problem】 Current issue encountered
Health score 85, the actual number of rows in the table is about 37 million. It seems consistent with TiDB Bug List= - #3，来自 h5n1 - TiDB 的问答社区. To solve this problem, the cluster was upgraded from 5.1.1 to 6.1.1, but it seems that the in-place upgraded cluster still has this issue.
±-------------------------±---------------±---------------±--------+
| Db_name | Table_name | Partition_name | Healthy |
±-------------------------±---------------±---------------±--------+
| testdb | test | | 85 |
±-------------------------±---------------±---------------±--------+
mysql> show stats_meta where table_name like ‘test’;
±-------------------------±---------------±---------------±--------------------±-------------±----------+
| Db_name | Table_name | Partition_name | Update_time | Modify_count | Row_count |
±-------------------------±---------------±---------------±--------------------±-------------±----------+
| testdb | test | | 2022-10-24 11:42:27 | 5392072 | 36269116 |
±-------------------------±---------------±---------------±--------------------±-------------±----------+
| id | estRows | actRows | task | access object | execution info | operator info | memory | disk |
±--------------------------±--------±---------±----------±------------------------------------------------------------------------±-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------±------------------------------------------------±--------±-----+
| StreamAgg_12 | 1.00 | 1 | root | | time:6.59s, loops:2 | funcs:count(1)->Column#82 | 8.38 KB | N/A |
| └─IndexReader_22 | 0.00 | 31162911 | root | | time:5.69s, loops:30601, cop_task: {num: 97, max: 2.95s, min: 67.5ms, avg: 885.8ms, p95: 2.4s, max_proc_keys: 1259990, p95_proc_keys: 1092213, tot_proc: 1m10s, tot_wait: 11.8s, rpc_num: 97, rpc_time: 1m25.9s, copr_cache_hit_ratio: 0.08} | index:IndexRangeScan_21 | 23.8 MB | N/A |
| └─IndexRangeScan_21 | 0.00 | 31162911 | cop[tikv] | table:t_hotel_source, index:ix_source_timestamp_12(source_timestamp_12) | tikv_task:{proc max:1.44s, min:223ms, p80:722ms, p95:1.1s, iters:30660, tasks:97}, scan_detail: {total_process_keys: 28869904, total_process_keys_size: 1328015584, total_keys: 72875098, rocksdb: {delete_skipped_count: 299421, key_skipped_count: 73168688, block: {cache_hit_count: 15074, read_count: 29515, read_byte: 757.1 MB}}} | range:(1666407599,1666580400), keep order:false | N/A | N/A |
【Business Impact】
【TiDB Version】
6.1.1
【Application Software and Version】
【Attachments】 Relevant logs and configuration information
- TiUP Cluster Display information
- TiUP Cluster Edit config information
Monitoring (https://metricstool.pingcap.com/)
- TiDB-Overview Grafana monitoring
- TiDB Grafana monitoring
- TiKV Grafana monitoring
- PD Grafana monitoring
- Corresponding module logs (including logs 1 hour before and after the issue)
If the question is related to performance optimization or fault troubleshooting, please download the script and run it. Please select all and copy-paste the terminal output.
|
username: