MySQL Bugs: #10028: mysqld hangs with 100% CPU consumption

Bug #10028	mysqld hangs with 100% CPU consumption
Submitted:	20 Apr 2005 11:49	Modified:	26 Jul 2005 9:21
Reporter:	Dmitry Kirilin	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.1.7	OS:	Linux (Red Hat Linux 9)
Assigned to:		CPU Architecture:	Any

Description:
After uptime of more than 3 months mysql server configured as replication master freezed and consumed 99.9% of CPU time.
Browsing logs, I found that this situation was occured several times during last week, but these hangs were short (20-60 sec) and not fatal. Last time it hang more than 3 minutes.
I had to resume service immediately and tried to restart it. "service mysqld stop" failed.
Then I used a brute method: "killall mysqld&&service mysqld start".
After that mysql resumed normal operation. Some pending queries was not executed, data loss occured.

How to repeat:
This situation may repeat, but I see no reason to wait next 3 month to supply the bug report with "how to repeat". I am planning an upgrade to 4.1.x: sometimes "newer is better".

Hi!

Can you please update this bug-report and add a comment saying how to reproduce the bug once you find a way to repeat it ?

Thanks.

Situation repeated.
There were some simultaneous "select" and "insert" queries, at some moment they all went in "Locked" state (I don't use table locks!).
MySQL hang and consumed 100% CPU.
"Unlock tables" was useless.
"service mysqld stop" has no effect.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

does it seems similar the bug 
 http://bugs.mysql.com/bug.php?id=10551  ?

Could you check attachements for that bug and estimate if it's the same bug as bug you hit ?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".