Bug #11994 | mysql 4.1.12 deadlock on a SMP box | ||
---|---|---|---|
Submitted: | 18 Jul 2005 4:30 | Modified: | 22 Oct 2005 6:51 |
Reporter: | Sivakumar K | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 4.1.12 | OS: | Linux (Redhat Enterprise Linux 3) |
Assigned to: | CPU Architecture: | Any |
[18 Jul 2005 4:30]
Sivakumar K
[18 Aug 2005 23:22]
Shawn Mitchell
Just an FYI, I'm seeing this on CentOS 4.0, with latests patches applied (RHE4.0) running on a Dell 6600 with 4 2.8Ghz Xeon CPU's, HT Enabled, and 8GB ram. (OS see's 8CPU's) Server version: 4.1.10a Protocol version: 10 mysql-server-4.1.10a-2.RHEL4.1 If 2+ queries are passed through at the same time, the queries deadlock, the CPU usage goes to 99% CPU usage. Other queries will go through just fine, but if two more queries exactly the same hit at exactly the same time, those too deadlock. I have 3 threads currently deadlocked for 2 hours now.
[22 Sep 2005 6:51]
Valeriy Kravchuk
Thank you for your bug report. Have you experienced the same behaviour with other (newer) versions of MySQL (4.1.14, 5.0.x?) and with other storage engines, or it is a BDB-specific problem only? Have you tried to repeat it without Java, using 2 standard mysql client session?
[22 Oct 2005 23:00]
Bugs System
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".