仍然在我的进程列表中被杀死的进程

时间:2021-04-18 20:25:17

The thread that I killed is still on my thread list How do I eliminate it?

我杀死的线程仍在我的线程列表中如何消除它?

+-----+------+-----------+-------------+---------+-------+-----------+------------------------------------------------------------------------------------------------------+
| Id  | User | Host      | db          | Command | Time  | State     | Info                                                                                                 |
+-----+------+-----------+-------------+---------+-------+-----------+------------------------------------------------------------------------------------------------------+
| 678 | root | localhost | hthtthv     | Killed  | 36923 | query end | INSERT INTO `gtgttg` VALUES (1,'tgtg'),(2,'Shopping'),(4,'tgtgtg'),(          |
| 695 | root | localhost | NULL        | Query   |     0 | NULL      | show processlist                                                                                     |
+-----+------+-----------+-------------+---------+-------+-----------+------------------------------------------------------------------------------------------------------+
2 rows in set (0.00 sec)

2 个解决方案

#1


17  

It needs to revert the actions it did, so this can take a long time. If it is an INNODB database, you can for instance look at this question: https://dba.stackexchange.com/questions/5654/internal-reason-for-killing-process-taking-up-long-time-in-mysql

它需要恢复它所做的动作,所以这可能需要很长时间。如果它是INNODB数据库,您可以查看这个问题:https://dba.stackexchange.com/questions/5654/internal-reason-for-killing-process-taking-up-long-time-in- MySQL的

So in the end: you need to wait for it to be eliminated

所以最后:你需要等待它被淘汰

#2


2  

In my case, my /var partition was full, where the MySQL binlogs are written. Once I freed some disk space, the killed connections immediately went away.

就我而言,我的/ var分区已满,其中写入了MySQL binlogs。一旦我释放了一些磁盘空间,被杀死的连接立即就消失了。

#1


17  

It needs to revert the actions it did, so this can take a long time. If it is an INNODB database, you can for instance look at this question: https://dba.stackexchange.com/questions/5654/internal-reason-for-killing-process-taking-up-long-time-in-mysql

它需要恢复它所做的动作,所以这可能需要很长时间。如果它是INNODB数据库,您可以查看这个问题:https://dba.stackexchange.com/questions/5654/internal-reason-for-killing-process-taking-up-long-time-in- MySQL的

So in the end: you need to wait for it to be eliminated

所以最后:你需要等待它被淘汰

#2


2  

In my case, my /var partition was full, where the MySQL binlogs are written. Once I freed some disk space, the killed connections immediately went away.

就我而言,我的/ var分区已满,其中写入了MySQL binlogs。一旦我释放了一些磁盘空间,被杀死的连接立即就消失了。