Opened 11 years ago
Closed 11 years ago
#327 closed defect (fixed)
Per-user sql connection limit
| Reported by: | adehnert | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | sql | Keywords: | |
| Cc: |
Description
We relatively often hit the cap on number of database connections. We should set max_user_connections (http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_max_user_connections; http://dev.mysql.com/doc/refman/5.0/en/user-resources.html) in addition to max_connections (http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_max_connections). Hopefully, this will mean that a single runaway account doesn't block other users from accessing sql.mit.edu.
This was previously brought up on -c scripts -i 2129340 on Sept. 26, 2012.
Change History (2)
comment:1 Changed 11 years ago by adehnert
comment:2 Changed 11 years ago by adehnert
- Resolution set to fixed
- Status changed from new to closed
I set max_user_connections to 128 in the live mysqld and in the config file on k-s and s-b, and successfully restarted k-s's mysqld. This is (hopefully) fixed. We'll see if it reduces our sql.mit.edu "too many connections" errors.
max_connections is currently 512. I propose setting max_user_connections to, oh, 128.