The "kill tidb" command is not effective

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

Original topic: kill tidb 不生效

| username: 开心大河马

【TiDB Usage Environment】Production Environment
【TiDB Version】
| tidb_version()
| Release Version: v6.5.1
Edition: Community
Git Commit Hash: 4084b07
Git Branch: heads/refs/tags/v6.5.1
UTC Build Time: 2023-03-07 16:12:08
GoVersion: go1.19.5
Race Enabled: false
TiKV Min Version: 6.2.0-alpha
Check Table Before Drop: false
Store: tikv |
【Reproduction Path】

【Encountered Problem: Problem Phenomenon and Impact】
log on the actual tidb server:10.xxx.xxx.236 which the long query executes on.
[root@10.xxx.xxx.236][4000][(none)][10:43:26]> select * FROM INFORMATION_SCHEMA.CLUSTER_PROCESSLIST where user =‘root’ and time >3600\G
*************************** 1. row ***************************
INSTANCE: 10.xxx.xxx.236:10080
ID: 5313049092622920637
USER: root
HOST: 10.xxx.xxx.231:48346
DB: xxxhdb
COMMAND: Query
TIME: 1031339
STATE: autocommit
INFO: show table t_txx_p2019 regions
DIGEST: 5b88eacbdcc92c783184fa5d9ff84ff9310992fa76e75bcae33ef77e93255050
MEM: 0
DISK: 0
TxnStart:
1 row in set (0.01 sec)

[root@10.xxx.xxx.236][4000][(none)][10:43:34]> kill tidb 5313049092622920637;
Query OK, 0 rows affected (0.00 sec)

[root@10.xxx.xxx.236][4000][(none)][10:43:45]> select * FROM INFORMATION_SCHEMA.CLUSTER_PROCESSLIST where user =‘root’ and time >3600\G
*************************** 1. row ***************************
INSTANCE: 10.xxx.xxx.236:10080
ID: 5313049092622920637
USER: root
HOST: 10.xxx.xxx.231:48346
DB: xxxhdb
COMMAND: Query
TIME: 1031352
STATE: autocommit
INFO: show table t_txx_p2019 regions
DIGEST: 5b88eacbdcc92c783184fa5d9ff84ff9310992fa76e75bcae33ef77e93255050
MEM: 0
DISK: 0
TxnStart:
【Resource Configuration】
3PD+2TIDB+8TIKV, 16core32g virtual machine
【Attachments: Screenshots/Logs/Monitoring】

| username: tidb菜鸟一只 | Original post link

Sometimes it happens, probably need to restart the corresponding TiDB node.

| username: 胡杨树旁 | Original post link

We also encountered this problem and had to restart the node.

| username: 开心大河马 | Original post link

Alright, I’ll restart it later. Thank you.

| username: 孤君888 | Original post link

Directly kill the TiDB Server process.

| username: redgame | Original post link

Decisively restart.

| username: xingzhenxiang | Original post link

Try reloading the corresponding TiDB server node.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.