I don't have the full anymore. It had a few hundred of these. I had issues a drop database that hung which made me run show processlist. Sadly, I did not check the processlist beforehand.
| 101189 | monitor | localhost:42585 | NULL | Query | 4079 | NULL | SHOW /*!50000 ENGINE */ INNODB STATUS | 0 | 0 | 1 | | 101194 | monitor | localhost:42589 | NULL | Query | 4069 | NULL | SHOW /*!50000 ENGINE */ INNODB STATUS | 0 | 0 | 1 | | 101204 | monitor | localhost:42599 | NULL | Query | 4049 | executing | SHOW /*!50000 GLOBAL */ STATUS | 0 | 0 | 1 | | 101214 | monitor | localhost:42608 | NULL | Query | 4029 | executing | SHOW /*!50000 GLOBAL */ STATUS | 0 | 0 | 1 | wait_timeout | 28800 max_connections | 5000 Since I sent this email, we have checked network connectivity and fixed a typo in the hostname. On Thu, Oct 25, 2012 at 1:56 PM, Rick James <[email protected]> wrote: > What does SHOW FULL PROCESSLIST say? > > What values do you have for > max_connections > wait_timeout (GLOBAL version) > > > -----Original Message----- > > From: Sabika M [mailto:[email protected]] > > Sent: Thursday, October 25, 2012 11:44 AM > > To: [email protected] > > Subject: MySQL Monitor and Percona > > > > We are in the process of switching to percona binaries of MySQL . I am > > using Percona 5.5.27 and monitoring the MySQL server with the MySQL > > Enterprise monitor. It starts up fine, but after a while I end up with > > MySQL monitor connections stacking up until the server becomes pretty > > much useless. This happens only on servers running percona. Anyone else > > have this issue? Or heard of it? Anything helps! >
