Custom Query (196 matches)

Now that #327 is fixed, we're somewhat less likely to notice when one user (probably hacked or DoSed?) is using a ton of connections. We should add monitoring of used connections, either max connections per user or total connections.

The check_mysql_query plugin in combination with the PROCESSLIST table in the information_schema database may be useful.

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.

web_scripts is sorta an annoying name and contributes to clutter in people's lockers. We should move away from it. (See also #263, although I don't believe there's any particular ordering constraint here.)