Bug #65468 | A couple of rows in tbl had write locks that couldn't be cleared | ||
---|---|---|---|
Submitted: | 30 May 2012 20:48 | Modified: | 28 Feb 2013 19:00 |
Reporter: | Greg Kemnitz | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 5.5.14-enterprise-commercial-advanced-lo | OS: | Solaris (innodb) |
Assigned to: | CPU Architecture: | Any | |
Tags: | foreign key, innodb, write lock |
[30 May 2012 20:48]
Greg Kemnitz
[30 May 2012 20:49]
Greg Kemnitz
oops - fix subject
[31 May 2012 9:45]
Valeriy Kravchuk
Check that bug you referenced, probably number is wrong (it's a Workbench bug). If you have the output of SHOW ENGINE INNODB STATUS and any other information from the moment when you had the problem, please, upload it to this bug report.
[31 May 2012 18:52]
Greg Kemnitz
SHOW ENGINE INNODB STATUS output
Attachment: innodb_out.txt (text/plain), 27.08 KiB.
[31 May 2012 18:53]
Greg Kemnitz
SHOW FULL PROCESSLIST output
Attachment: show_full_processlist.txt (text/plain), 10.91 KiB.
[31 May 2012 18:56]
Greg Kemnitz
You're right that the bug number above is wrong. The right bug number for the error we saw when we killed the updates was Bug 64556.
[30 Jan 2013 19:00]
Sveta Smirnova
Thank you for the feedback. Please try with current version 5.5.29 and if issue is repeatable provide us output of SHOW CREATE TABLE for table ga_ra_user and all, linked with foreign keys.
[1 Mar 2013 1: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".