*: skip log timeout on maxExecutiontime as slow query for DDL statement.

[Benjamin2037]

What problem does this PR solve?

When user issue an long run DDL statement, it should not be checked in maxExecutionTime for slow query checking mechanism.

Issue Number: close #38580

Problem Summary:
Just Skip none query type statements max execution time checking and kill them.

What is changed and how it works?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• hawkingrei
• xhebox

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[xhebox]

LGTM, but we do have descriptions:

Unlike in MySQL, the max_execution_time system variable currently works on all kinds of statements in TiDB, not only restricted to the SELECT statement. The precision of the timeout value is roughly 100ms. This means the statement might not be terminated in accurate milliseconds as you specify.

https://docs.pingcap.com/tidb/dev/system-variables#max_execution_time

This should be investigated.

[Benjamin2037]

LGTM, but we do have descriptions:

Unlike in MySQL, the max_execution_time system variable currently works on all kinds of statements in TiDB, not only restricted to the SELECT statement. The precision of the timeout value is roughly 100ms. This means the statement might not be terminated in accurate milliseconds as you specify.

https://docs.pingcap.com/tidb/dev/system-variables#max_execution_time

This should be investigated.

This Note is not correct, currently we do not support max_execution_time on all kinds of statements in TiDB.

[xhebox]

LGTM, but we do have descriptions:

Unlike in MySQL, the max_execution_time system variable currently works on all kinds of statements in TiDB, not only restricted to the SELECT statement. The precision of the timeout value is roughly 100ms. This means the statement might not be terminated in accurate milliseconds as you specify.

https://docs.pingcap.com/tidb/dev/system-variables#max_execution_time
This should be investigated.

This Note is not correct, currently we do not support max_execution_time on all kinds of statements in TiDB.

#10541 According to this PR, I think your argument makes more sense. Then https://github.com/pingcap/docs-cn/blob/master/develop/dev-guide-timeouts-in-tidb.md and its english version needs to be modified along this PR.

[hawkingrei]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: f3d2466

[wuhuizuo]

/run-build
/run-mysql-test

[wuhuizuo]

/run-build
/run-mysql-test

[sre-bot]

TiDB MergeCI notify

✅ Well Done! New fixed [1] after this pr merged.

CI Name	Result	Duration	Compare with Parent commit
idc-jenkins-ci-tidb/integration-compatibility-test	✅ all 1 tests passed	2 min 34 sec	Fixed
idc-jenkins-ci-tidb/integration-ddl-test	🟢 all 6 tests passed	28 min	Existing passed
idc-jenkins-ci/integration-cdc-test	🟢 all 38 tests passed	21 min	Existing passed
idc-jenkins-ci-tidb/integration-common-test	🟢 all 17 tests passed	10 min	Existing passed
idc-jenkins-ci-tidb/common-test	🟢 all 11 tests passed	9 min 6 sec	Existing passed
idc-jenkins-ci-tidb/tics-test	🟢 all 1 tests passed	5 min 46 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-2	🟢 all 28 tests passed	5 min 36 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-1	🟢 all 26 tests passed	4 min 54 sec	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	2 min 54 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed