Warning: file_get_contents(/data/phpspider/zhask/data//catemap/8/mysql/68.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
如何清理休眠的mysql进程?_Mysql_Ruby On Rails 4_Timeout - Fatal编程技术网

如何清理休眠的mysql进程?

如何清理休眠的mysql进程?,mysql,ruby-on-rails-4,timeout,Mysql,Ruby On Rails 4,Timeout,我有一个rails 4应用程序的问题,它会留下空闲的mysql连接。当我们查看代码以确定原因时,我至少希望能够自动消除有问题的进程。mysql文档说设置wait_timeout和interactive_timeout将关闭非活动连接,所以我将它们都设置为300。然而,如下文所示,存在超过300极限的各种过程。我已经确认设置确实是300。为什么mysql不消除这些进程 mysql> show processlist; +-----+--------------+-----------+------

我有一个rails 4应用程序的问题,它会留下空闲的mysql连接。当我们查看代码以确定原因时,我至少希望能够自动消除有问题的进程。mysql文档说设置wait_timeout和interactive_timeout将关闭非活动连接,所以我将它们都设置为300。然而,如下文所示,存在超过300极限的各种过程。我已经确认设置确实是300。为什么mysql不消除这些进程

mysql> show processlist; +-----+--------------+-----------+--------------+---------+------+-------+------------------+ | Id | User | Host | db | Command | Time | State | Info | +-----+--------------+-----------+--------------+---------+------+-------+------------------+ | 143 | application | localhost | application | Sleep | 1500 | | NULL | | 144 | application | localhost | application | Sleep | 1499 | | NULL | | 145 | application | localhost | application | Sleep | 0 | | NULL | | 146 | application | localhost | application | Sleep | 780 | | NULL | | 147 | application | localhost | application | Sleep | 783 | | NULL | | 148 | application | localhost | application | Sleep | 0 | | NULL | | 149 | application | localhost | application | Sleep | 7 | | NULL | | 150 | application | localhost | application | Sleep | 3 | | NULL | | 151 | application | localhost | application | Sleep | 8 | | NULL | | 152 | application | localhost | application | Sleep | 3 | | NULL | | 155 | root | localhost | NULL | Query | 0 | NULL | show processlist | +-----+--------------+-----------+--------------+---------+------+-------+------------------+ 11 rows in set (0.00 sec) mysql>显示进程列表; +-----+--------------+-----------+--------------+---------+------+-------+------------------+ |Id |用户|主机| db |命令|时间|状态|信息| +-----+--------------+-----------+--------------+---------+------+-------+------------------+ |143 |应用程序|本地主机|应用程序|睡眠| 1500 |空| |144 |应用程序|本地主机|应用程序|睡眠| 1499 |空| |145 |应用程序|本地主机|应用程序|睡眠| 0 | |空| |146 |应用程序|本地主机|应用程序|睡眠| 780 |空| |147 |应用程序|本地主机|应用程序|睡眠| 783 |空| |148 |应用程序|本地主机|应用程序|睡眠| 0 | |空| |149 |应用程序|本地主机|应用程序|睡眠| 7 | |空| |150 |应用程序|本地主机|应用程序|睡眠| 3 | |空| |151 |应用程序|本地主机|应用程序|睡眠| 8 | |空| |152 |应用程序|本地主机|应用程序|睡眠| 3 | |空| |155 | root | localhost | NULL | Query | 0 | NULL | show processlist| +-----+--------------+-----------+--------------+---------+------+-------+------------------+ 一组11行(0.00秒)
尝试运行mysql查询
kill 143


这对我很有用

试着运行mysql查询
kill 143


这对我有效

请检查您的RoR连接池。这些进程可能表示MySQL连接被该池保持打开状态。您可以激活常规日志并检查其内容,以查看是否从每个连接接收到任何内容。请检查您的RoR连接池。这些进程可能表示MySQL连接被该池保持打开状态。您可以激活常规日志并检查其内容,以查看是否从每个连接接收到任何内容。