Bug #38188 | Replication deadlock | ||
---|---|---|---|
Submitted: | 16 Jul 2008 23:04 | Modified: | 14 Oct 2008 16:06 |
Reporter: | Eric Thunberg | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S1 (Critical) |
Version: | 5.1.26 | OS: | Linux (CentOS release 5 (Final) x86_64) |
Assigned to: | CPU Architecture: | Any | |
Tags: | deadlock, myisam, replication |
[16 Jul 2008 23:04]
Eric Thunberg
[17 Jul 2008 5:36]
Sveta Smirnova
Thank you for the report. Dead lock itself can be probably not a bug, as it can happen. But is strange what you can not use KILL. Please provide output of SHOW CREATE TABLE servers, full SELECT statement and output of SHOW CREATE TABLE of all tables underlying for SELECT.
[17 Jul 2008 5:52]
Eric Thunberg
Debug data requested by Sveta Smirnova on 7/17/2008
Attachment: mysql_debug.txt (text/plain), 10.97 KiB.
[17 Jul 2008 5:54]
Eric Thunberg
As noted above, I've attached the requested information in the order you asked for it. Regarding the deadlock, I understand that they can occur I just find it strange that it's always with the replication thread. Please let me know if there's anything else you need.
[17 Jul 2008 15:37]
Eric Thunberg
It happened again last night, here is the debug output I captured.
Attachment: mysql_debug2.txt (text/plain), 21.79 KiB.
[14 Sep 2008 16:06]
Valeriy Kravchuk
Please, try to repeat with a newer version, 5.1.28, and inform about the results.
[14 Oct 2008 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".