TiDB 6.1.2 Dashboard Unable to View Slow Query Details SQL Error 1105: other error: Column ID 73 of table cluster_slow_query not found

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tidb6.1.2 dashboard 看不了慢查询明细sql Error 1105: other error: Column ID 73 of table cluster_slow_query not found

| username: heming

[TiDB Usage Environment] Production Environment / Test / Poc
Production
[TiDB Version]
6.1.2
[Reproduction Path] What operations were performed when the issue occurred
dashboard 6.1.2 Click on slow query details:
Slow Query Details
Error 1105: other error: Column ID 73 of table cluster_slow_query not found
[Encountered Issue: Issue Phenomenon and Impact]
show create table information_schema.cluster_slow_query;
Plan_from_binding tinyint(1) DEFAULT NULL,
Has_more_results tinyint(1) DEFAULT NULL, # 6.1.2 added this field, not sure why it caused an error.

[Resource Configuration]
[Attachments: Screenshots / Logs / Monitoring]

2
| username: jaybing926 | Original post link

There’s still such an error in 6.x? I encountered several errors in the 4.0.9 dashboard and thought it was because the version was too old.

3
| username: Jiawei | Original post link

This error looks like an internal error. You can file an issue for it.

4
| username: foxchan | Original post link

The dashboard anomaly is due to multiple versions of TiDB instances.

5
| username: qizheng | Original post link

Was it upgraded? The newly deployed v6.1.2 cluster doesn’t have this issue.

6
| username: 裤衩儿飞上天 | Original post link

I didn’t encounter this issue after my upgrade.

7
| username: 裤衩儿飞上天 | Original post link

5.4.1 → 6.1.2

8
| username: heming | Original post link

The issue is due to the compatibility problem with the ifnull function, which was caused by adding TiDB version 5.4.3. After replacing ifnull with case when and removing TiDB version 5.4.3, it worked fine.

9
| username: 裤衩儿飞上天 | Original post link

It seems that having multiple versions coexist in one cluster causes too many problems.

10
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.