Emergency root@localhost db connection and service

Registered by Nadeem on 2010-08-16

In cloud due to lack of the db engine to allocate resources fairly, we run into lots of situations of running out of connection handles.

During situations when max_connections is saturated, an Admin or a DBA is powerless to kill offending queries.
mysqladmin commands will also fail in such scenarios with a "too many connections".
Logging into the mysql client also yields the same error.
Usually what happens is that end users/customers queries that are long running or slow will start stacking up which will put more load on the server in turn slowing it for another (usually next slowest) customer queries which also start stacking up.
Eventually all connections are maxed out and we have no option but to recycle mysql service or kill the mysqld process which not desirable if it can be avoided.

I'd like to see if we can get Drizzle to implement a way of saving one extra connection at all times for "root@localhost" if no other "root@localhost" connections are already in place.
Sort of a super root@localhost user that has the edge for administrative use.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.