First of all if you're getting this error it is a result of extreme database activity. If you aren't expecting it or it doesn't make sense to you 99% of the time this is a database driven script being exploited (some common examples I see often are things like phpBB being hit by dozens, hundreds or thousands of bots making constant DB write requests).
The easiest way to identify this is to restart MySQL and then run the third party tool "mtop" and you'll see all the queries running and usually the problem DB jumps out at you as being up and active with so many queries that it's obvious (then work backwards and find out what programs, users or scripts are using the database).
There is also a way to periodically clear the session table and adjust the amount of sessions but that is not the long-term solution if it's abuse/DOS.
usr, libexec, mysqld, solutionfirst, database, aren, doesn, exploited, examples, phpbb, dozens, bots, db, requests, easiest, restart, mysql, quot, mtop, ll, queries, jumps, active, programs, users, scripts, periodically, adjust, sessions, dos,