TiDB Dashboard Top SQL500 Error

Translated
1

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

Original topic: TIDB的dashboard Top SQL500报错

| username: 末日温度

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version] v6.5.1
[Reproduction Path] Operations performed that led to the issue
After the server restarted due to a power outage
[Encountered Issue: Problem Phenomenon and Impact]
Wanted to view the Top SQL rankings, but the page directly displayed the following content
Error
API: /topsql/instances
Request failed with status code 500
[Resource Configuration]
[Attachment: Screenshot/Log/Monitoring]

image
image1380×668 30.2 KB

2
| username: 芮芮是产品 | Original post link

There are too many slow SQLs. Go delete and clean up the slow log.

3
| username: TiDBer_OB4kHrS7 | Original post link

This data is in memory, right? It will be gone after a restart, right?

4
| username: 末日温度 | Original post link

Part of the show log has been cleared and some TiDB log files have been deleted, but the issue persists.

5
| username: TiDBer_QYr0vohO | Original post link

Take a look at the PD logs, it’s best to change them to debug level logs.

6
| username: 考试没答案 | Original post link

I remember that switching the PD leader should work. Give it a try. There’s a similar post.

7
| username: 末日温度 | Original post link

Do you have a link?

8
| username: dbaspace | Original post link

Switch PD leader: member leader transfer pd3 // pd3 is the new leader to transfer to

9
| username: 末日温度 | Original post link

Here are some error logs.

10
| username: 考试没答案 | Original post link

Is it working normally now?

11
| username: TiDBer_QYr0vohO | Original post link

You can follow what the brother above said and switch the PD leader.

12
| username: 末日温度 | Original post link

The issue with switching the leader still persists.

Here is the statement for a successful switch:
» member leader transfer pd-10.20.60.133-2379
Success!

13
| username: tidb菜鸟一只 | Original post link

Use tiup cluster display <cluster_name> to check the status of PD and Dashboard.

14
| username: 末日温度 | Original post link

The operation is normal.

15
| username: TiDBer_小阿飞 | Original post link

Changing the PD leader node, just not sure about the logic and principles.

16
| username: 路在何chu | Original post link

Restart the PD, then switch to the leader.

17
| username: 随缘天空 | Original post link

A 500 error is generally a server issue. Use tiup cluster display <cluster-name> to check if all nodes in the cluster are functioning properly. Then, restart the problematic nodes. If that doesn’t work, try restarting the entire cluster service.

18
| username: heiwandou | Original post link

Try switching the PD and see.

19
| username: 末日温度 | Original post link

All nodes are displayed in green and normal, no issues!~

20
| username: 末日温度 | Original post link

Switched the PD leader, but the problem remains. Restarted the entire database service, but the problem still persists. I’m at a loss and don’t know how to handle it.