Joe, ----- Original Message ----- From: "Joe Shear" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Wednesday, July 23, 2003 10:40 PM Subject: RE: mysql stops processing
> hi, > > We're pretty careful about preventing that. Also, no queries are moving > forward, no inserts, updates, or selects, even the ones on tables that > are only a mixture of inserts and selects. what do SHOW PROCESSLIST and SHOW INNODB STATUS print in this situation? Or is it so that you cannot run them because of maxed out connections? You could write script to run them every 5 seconds so that we could see what is happening. Also, if you do CREATE TABLE innodb_monitor(a INT) TYPE=InnoDB; then mysqld will print the output of SHOW INNODB STATUS to the .err file every 15 seconds. What is the CPU usage from 'top' during the hang? 4.0.14 has better diagnostics than 3.23.56. An upgrade might help, but let us wait a couple of days first. > joe Regards, Heikki > On Wed, 2003-07-23 at 12:02, Andrew Braithwaite wrote: > > Hi, > > > > I don't know what type of applications are using your database but if I had > > to guess at the problem, I would guess that you have a very slow query which > > runs every now and again that is locking up certain tables/records causing > > all the other queries to queue up and eventually running out of connections > > on the DB. To find out if this is the case, when your server gets into this > > state run a "mysqladmin -v pro" and see if all the queries are waiting for a > > lock to be freed up. > > > > Hope this helps, > > > > Andrew > > > > -----Original Message----- > > From: Joe Shear [mailto:[EMAIL PROTECTED] > > Sent: Wednesday 23 July 2003 19:45 > > To: [EMAIL PROTECTED] > > Subject: mysql stops processing > > > > > > Hi, > > > > Has anyone ever had any problems with MySQL w/ all InnoDB tables just stop > > processing queries? There doesn't seem to be any pattern to it, it happens > > at times of relatively high load (load avg of 4 on a dual proc) but the CPUs > > still have plenty of idle time, and the disks aren't maxing out. It doesn't > > happen everytime there is a high load either. The box just stops processing > > every query, and we quickly hit the max connection limit. The only solution > > we've found is to shutdown mysql and restart it -- at which point it works > > fine for a couple days. We are running mysql 3.23.56 w/ redhat 7.3 and > > 2.4.20 kernel. Anybody have any suggestions? > > > > thanks, > > joe > -- > Joe Shear <[EMAIL PROTECTED]> > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
