48

I see a lot of connections are open and remain idle for a long time, say 5 minutes.

Is there any solution to terminate / close it from server without restarting the mysql service?

I am maintaining a legacy PHP system and can not close the connections those are established to execute the query.

Should I reduce the timeout values in my.cnf file those defaults to 8 hours?

# default 28800 seconds

interactive_timeout=60
wait_timeout=60
Konerak
  • 39,272
  • 12
  • 98
  • 118
shantanuo
  • 31,689
  • 78
  • 245
  • 403

2 Answers2

73

Manual cleanup:

You can KILL the processid.

mysql> show full processlist;
+---------+------------+-------------------+------+---------+-------+-------+-----------------------+
| Id      | User       | Host              | db   | Command | Time  | State | Info                  |
+---------+------------+-------------------+------+---------+-------+-------+-----------------------+
| 1193777 | TestUser12 | 192.168.1.11:3775 | www  | Sleep   | 25946 |       | NULL                  |
+---------+------------+-------------------+------+---------+-------+-------+-----------------------+

mysql> kill 1193777;

But:

  • the php application might report errors (or the webserver, check the error logs)
  • don't fix what is not broken - if you're not short on connections, just leave them be.

Automatic cleaner service ;)

Or you configure your mysql-server by setting a shorter timeout on wait_timeout and interactive_timeout

mysql> show variables like "%timeout%";
+--------------------------+-------+
| Variable_name            | Value |
+--------------------------+-------+
| connect_timeout          | 5     |
| delayed_insert_timeout   | 300   |
| innodb_lock_wait_timeout | 50    |
| interactive_timeout      | 28800 |
| net_read_timeout         | 30    |
| net_write_timeout        | 60    |
| slave_net_timeout        | 3600  |
| table_lock_wait_timeout  | 50    |
| wait_timeout             | 28800 |
+--------------------------+-------+
9 rows in set (0.00 sec)

Set with:

set global wait_timeout=3;
set global interactive_timeout=3;

(and also set in your configuration file, for when your server restarts)

But you're treating the symptoms instead of the underlying cause - why are the connections open? If the PHP script finished, shouldn't they close? Make sure your webserver is not using connection pooling...

Community
  • 1
  • 1
Konerak
  • 39,272
  • 12
  • 98
  • 118
  • can I use this command on a shared host such as hostgator? I want to reduce the chance of maxing out my mysql connections and getting a TOS email/shutdown. – hamish Jan 31 '16 at 00:00
3

I don't see any problem, unless you are not managing them using a connection pool.

If you use connection pool, these connections are re-used instead of initiating new connections. so basically, leaving open connections and re-use them it is less problematic than re-creating them each time.

guykaplan
  • 145
  • 1
  • 3
  • can you please suggest how can one reuse the existing open/idle connections instead of creating new one. I am using spring boot 2.1.4 + Hikari cp + mariadb 10.3. Is there any way to configure the reuse property for database connection. – s developer Sep 30 '20 at 10:22