Help Center/ TaurusDB/ Troubleshooting/ Basic Issues/ No Scanned Rows Recorded in Slow Query Logs

Updated on 2024-09-05 GMT+08:00

View PDF

No Scanned Rows Recorded in Slow Query Logs

Scenario

In slow query logs, an SQL statement was executed for 65 seconds, but the number of scanned rows was 0.

Possible Causes

If an SQL statement is interrupted but its execution time exceeds the slow log threshold, the statement will be recorded in slow query logs and the number of scanned rows is 0. Timeout thresholds have been configured for the JDBC connection from the client.

Solution

Optimize the SQL statement or set socketTimeout to an appropriate value.

Parent topic: Basic Issues

Previous topic: Impact of Creating an Empty Username

Next topic: "handle_sync_msg_from_slave my_net_read error:-1" Displayed on the Error Logs Tab Page

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.