List:General Discussion« Previous MessageNext Message »
From:David Johnson Date:May 11 1999 5:08pm
Subject:Re: Quickie
View as plain text  
No.  We manage  so when it goes down, the site
stops, we panic and restart the db as fast as possible.  We think we found a
locking problem in our DBI code that caused a locking issue with our main
User table.  If it happens again (God forbid)  I'll try 'mysqladmin proc'.

----- Original Message -----
From: Michael Widenius <monty@stripped>
To: David Johnson <davej@stripped>
Cc: <mysql@stripped>
Sent: Tuesday, May 11, 1999 7:40 AM
Subject: Quickie

> >>>>> "David" == David Johnson <davej@stripped> writes:
> David> We had our production database go bezerk and take 100% of the CPU
for about 5 minutes before we had to kill it.  There is speculation that we
had some table locking contention, but it seems to me that a bad lock
wouldn't cause the locked threads to sleep and wait instead of eating all
the CPU.  Am I right?
> Normally bad locking will put all threads to sleep, but there are
> always exceptions to this rule.
> Did you manage to do a 'mysqladmin proc' when this happen?
> Regards,
> Monty

QuickieDavid Johnson11 May
  • QuickieMichael Widenius11 May
  • Re: QuickieDavid Johnson11 May