Comment 0 for bug 893348

Hello

We are using max_user_connections=30 to prevent too many connections by user mistake.
Three weeks ago we upgraded 6 servers to Percona-Server-5.5 from 5.1.

And right after upgrade we noticed a problem with max_user_connections on all upgraded servers.

Users that connects to database very often, started to experience problem:
User ***** already has more than 'max_user_connections' active connections
But "SHOW PROCESSLIST" did not list any active connections for this user!

How you know, 5.5 has max_user_connections in mysql.user table.
We put max_user_connections=30 into this table, instead of global variable and nothing changes.

Known symptoms:
- Problem does not come up after mysql restart. It takes some time.
- "flush privileges" helps to reset counter, but after few hours issue is active again.

It fills like max_user_connections counter for specific (very active) users doesn't reset for some bug reason.

Server hardware:
32GB RAM. 4x4 core CPUs, SAS HDDS in RAID1 for /var/lib/mysql.
OS: centos5 x86_64

I am ready to provide any information that will help to find and resolve this issue.

Thank you.

Regards,
Gor