-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
TiDB can't close connection immediately after killing client process #57531
Comments
/report customer |
The sleep command can be killed by "kill" command. It seems the killing of client doesn't send kill signal to the target sleep process. I think this should be a sql infra issue. |
/sig infra |
@yibin87: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/sig sql-infra |
/remove-sig execution |
This is what go-sql-driver/mysql uses: https://github.com/go-sql-driver/mysql/blob/v1.8.1/conncheck.go |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Run a tidb instance locally, and execute
select sleep(300);
in a connection.Then kill this client process
ps aux | grep -i mysql | grep -v grep | awk '{print $2}' | xargs kill
2. What did you expect to see? (Required)
The connection is closed immediately like mysql.
3. What did you see instead (Required)
The connection is still in processlist and closed after 300s of execution.
4. What is your TiDB version? (Required)
v8.2.0
The text was updated successfully, but these errors were encountered: