Shawn Green wrote:
What you might be seeing is the "purge" process of the InnoDB engine.
http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html#option_mysqld_innodb_max_purge_lag
and from
http://dev.mysql.com/doc/refman/5.0/en/innodb-multi-versioning.html
>>In a scenario where the use
Hello Ben,
Ben Clewett wrote:
No worries :)
> Good luck with your problem!
Apparently not, since no member of the MySql team wants to tell me and
this mailing list what scenario's will cause a low-load MySql system
lock at 100% CPU for hours on end.
Another of my servers has just entered
No worries :)
> Good luck with your problem!
Apparently not, since no member of the MySql team wants to tell me and
this mailing list what scenario's will cause a low-load MySql system
lock at 100% CPU for hours on end.
Another of my servers has just entered this mode about half an hour ago.
At 12:08p -0500 on 17 Jan 2008, Ben Clewett wrote:
The package you show gives the same output as the 'SHOW PROCESSLIST'
output, which I included in my previous email :)
Heh, that'll teach me to actually /use/ the package before recommending
it. :-P (I just found out about it when that article
Hi Kevin,
Thanks for the advise.
The package you show gives the same output as the 'SHOW PROCESSLIST'
output, which I included in my previous email :)
The problem I have is that the process list, by 'mytop' or 'SHOW
PROCESSLIST' shows the server doing noting.
Yet 'top' and other tools show
At 3:25a -0500 on 17 Jan 2008, Ben Clewett wrote:
I need to know why MySql does this. If any person knows how I an
identify the problem, please let me know!
I think this package helped another person out on this list a couple
days ago:
http://debaday.debian.net/2007/12/26/mytop-a-top-clone-
Dear MySql,
I hope you can help me trace a problem.
Every few days one of my 5.0.45 will stick at 100% CPU whilst not doing
very much.
The server is a replication master and slave, but idle at this time. I
am running 100% InnoDB and there is nothing in the error log.
It will stay that way
