Bug #43569 MySQL deadlocks
Submitted: 11 Mar 2009 17:21 Modified: 19 Jan 2012 7:30
Reporter: Peteris Krumins Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Locking Severity:S1 (Critical)
Version:5.1.32 OS:Linux (x86_64 GNU/Linux)
Assigned to: CPU Architecture:Any
Tags: deadlock, innodb, lockup

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[11 Mar 2009 17:22] Peteris Krumins
output of `show innodb status`

Attachment: show-innodb-status.txt (text/plain), 63.44 KiB.

[17 Mar 2009 19:02] Peteris Krumins
show global status on enterprise mysql

Attachment: global-status-enterprise (application/octet-stream, text), 5.82 KiB.

[17 Mar 2009 19:02] Peteris Krumins
show global status on enterprise mysql

Attachment: global-status-enterprise (application/octet-stream, text), 5.82 KiB.

[17 Mar 2009 19:13] Peteris Krumins
innodb io graph

Attachment: innodb-io.png (image/png, text), 58.23 KiB.

[17 Mar 2009 19:13] Peteris Krumins
innodb insbuffer graph

Attachment: innodb-insbuffer.png (image/png, text), 50.63 KiB.

[17 Mar 2009 19:14] Peteris Krumins
innodb bufpgmem graph

Attachment: innodb-bufpgmem.png (image/png, text), 68.07 KiB.

[17 Mar 2009 19:14] Peteris Krumins
mysql threads graph

Attachment: mysql-threads.png (image/png, text), 51.06 KiB.