The query is stuck

Translated
1

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

Original topic: 查询卡死了

| username: emerson_cai

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]

I started a query on Navicat, but it never returned a result and eventually timed out. How can I troubleshoot this issue?

tidb_1
tidb_11380×758 403 KB

2
| username: Billmay表妹 | Original post link

Check the monitoring, look at the slow SQL, and try to optimize it.

Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page

Let’s see your configuration.

3
| username: Billmay表妹 | Original post link

Here are some possible reasons and solutions:

  1. Issues with the query itself: You can check if the query is correct and if there are any syntax or logical errors. You can try running the same query in the command line or other tools to confirm its correctness.
  2. Database connection issues: You can check if the database connection is normal. You can try connecting to the database using other tools to confirm the connection status. If there are connection issues, you can try reconnecting to the database or checking if the database configuration is correct.
  3. Database performance issues: You can check if the database performance is normal. You can try using other tools to perform performance tests on the database to confirm its performance. If there are performance issues, you can try optimizing the database configuration or increasing hardware resources.
  4. Network issues: You can check if the network connection is normal. You can try using other tools to test the network connection to confirm its status. If there are network issues, you can try reconnecting to the network or checking if the network configuration is correct.
  5. Long query execution time: You can check if the query execution time is too long. If the execution time is too long, it may lead to timeout failures. You can try optimizing the query or increasing database resources to improve query performance.
4
| username: tidb菜鸟一只 | Original post link

For your SQL, just add an index.