Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The KILL statement terminate a system table query connection for long time #57749

Closed
lilinghai opened this issue Nov 27, 2024 · 0 comments · Fixed by #57766
Closed

The KILL statement terminate a system table query connection for long time #57749

lilinghai opened this issue Nov 27, 2024 · 0 comments · Fixed by #57766
Assignees
Labels
affects-8.5 This bug affects the 8.5.x(LTS) versions. severity/moderate sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.

Comments

@lilinghai
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

millions tables
kill select count(*) from INFORMATION_SCHEMA.partitions;
it takes about 15 minutes kill the connection

[2024/11/27 03:45:34.419 +00:00] [WARN] [sqlkiller.go:61] ["kill initiated"] ["connection ID"=2405433398] [reason="[executor:1317]Query execution was interrupted"]
[2024/11/27 04:00:58.467 +00:00] [WARN] [sqlkiller.go:137] ["kill finished"] [conn=2405433398]

Same scenario for max_execution_time
set @@max_execution_time=1000;
select count(*) from INFORMATION_SCHEMA.partitions;
it takes about 17 minutes terminate the query

[2024/11/27 04:07:49.399 +00:00] [WARN] [expensivequery.go:97] ["execution timeout, kill it"] [costTime=17m24.497578181s] [maxExecutionTime=1s] [processInfo="{id:1579157424, user:root, host:10.200.0.166:60519, db:<nil>, command:Query, time:1044, state:autocommit, info:select count(*) from INFORMATION_SCHEMA.partitions}"]
[2024/11/27 04:07:49.399 +00:00] [INFO] [server.go:913] [kill] [conn=1579157424] [query=true] [maxExecutionTime=true] [runawayExceed=false]
[2024/11/27 04:07:49.499 +00:00] [WARN] [expensivequery.go:97] ["execution timeout, kill it"] [costTime=17m24.59749879s] [maxExecutionTime=1s] [processInfo="{id:1579157424, user:root, host:10.200.0.166:60519, db:<nil>, command:Query, time:1044, state:autocommit, info:select count(*) from INFORMATION_SCHEMA.partitions}"]
[2024/11/27 04:07:49.528 +00:00] [ERROR] [terror.go:317] ["function call errored"] [error="[executor:3024]Query execution was interrupted, maximum statement execution time exceeded"] 

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

master
dcc9dcc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-8.5 This bug affects the 8.5.x(LTS) versions. severity/moderate sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants