The process that was killed on my process list

The thread I killed is still on the topic list. How to fix 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) 
+7
source share
2 answers

He must return the actions he has taken, so this can take a long time. If it is an INNODB database, you can, for example, look at this question: https://dba.stackexchange.com/questions/5654/internal-reason-for-killing-process-taking-up-long-time-in- mysql

So at the end: you need to wait for it to be deleted

+17
source

In my case, the my / var section was populated with MySQL bing files. As soon as I freed up disk space, the killed connections immediately left.

+1
source

All Articles