show processlist:
| 101189 | mysql_monitor | localhost:42585 | NULL | Query | 4079 |
NULL | SHOW /*!50000 ENGINE */ INNODB
STATUS | 0 | 0 | 1 |
| 101194 | mysql_monitor | localhost:42589 | NULL | Query | 4069 |
NULL | SHOW /*!50000 ENGINE */ INNODB
STATUS | 0 | 0 | 1 |
| 101199 | mysql_monitor | localhost:42593 | NULL | Killed | 4059 |
executing | SHOW /*!50000 GLOBAL */
STATUS | 0 | 0 | 1 |
| 101204 | mysql_monitor | localhost:42599 | NULL | Query | 4049 |
executing | SHOW /*!50000 GLOBAL */
STATUS | 0 | 0 | 1 |
| 101209 | mysql_monitor | localhost:42603 | NULL | Killed | 4039 |
executing | SHOW /*!50000 GLOBAL */
STATUS | 0 | 0 | 1 |
| 101214 | mysql_monitor | localhost:42608 | NULL | Query | 4029 |
executing | SHOW /*!50000 GLOBAL */
STATUS | 0 | 0 | 1 |
| 101221 | mysql_monitor | localhost:42613 | NULL | Killed | 4019 |
executing | SHOW /*!50000 GLOBAL */
STATUS | 0 | 0 | 1 |
| 101226 | mysql_monitor | localhost:42617 | NULL | Killed | 4009 |
executing | SHOW /*!50000 GLOBAL */
STATUS | 0 | 0 | 1 |
| 101231 | mysql_monitor | localhost:42621 | NULL | Killed | 3999 |
executing | SHOW /*!50000 GLOBAL */
STATUS | 0 | 0 | 1 |
| 101236 | mysql_monitor | localhost:42626 | NULL | Killed | 3989 |
executing | SHOW /*!50000 GLOBAL */
STATUS | 0 | 0 | 1 |
| 101241 | mysql_monitor | localhost:42630 | NULL | Killed | 3979 |
executing | SHOW /*!50000 GLOBAL */
STATUS | 0 | 0 | 1 |
| 101246 | mysql_monitor | localhost:42635 | NULL | Killed | 3969 |
executing | SHOW /*!50000 GLOBAL */ STATUS
On Thu, Oct 25, 2012 at 12:21 PM, Justin Swanhart <
justin.swanh
...@percona.com> wrote:
> At a minimum you will need to provide a SHOW PROCESSLIST and SHOW ENGINE
> INNODB STATUS during the problem.
> --Justin
> On Thu, Oct 25, 2012 at 11:47 AM, Sabika M <sabika.makhd...@gmail.com>wrote:
>> 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!
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Percona Discussion" group.
>> To post to this group, send email to percona-discussion@googlegroups.com.
> --
> You received this message because you are subscribed to the Google Groups
> "Percona Discussion" group.
> To post to this group, send email to percona-discussion@googlegroups.com.