| Bug #20857 | Deadlocks detected by timeout (S L O W) | ||
|---|---|---|---|
| Submitted: | 5 Jul 2006 1:22 | Modified: | 15 May 2007 16:42 |
| Reporter: | David Sharnoff | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S5 (Performance) |
| Version: | 5.0.32-BK, 5.0.25-BK, 4.1.15 and 5.0.22 | OS: | Linux (Linux 2.6.15, Linux 2.6.12) |
| Assigned to: | Heikki Tuuri | CPU Architecture: | Any |
| Tags: | concurrency, deadlock, innodb, lock, performance | ||
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:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[5 Jul 2006 19:41]
David Sharnoff
[5 Jul 2006 19:44]
David Sharnoff
my.cnf from my Debian system (mysql 5.0.22)
Attachment: my.cnf (application/octet-stream, text), 3.44 KiB.
[19 Jan 2007 8:18]
Giuseppe Maxia
output of submitted material
Attachment: bug_20857_output.zip (application/zip, text), 39.33 KiB.
[22 Jan 2007 10:05]
Giuseppe Maxia
second run with additional information
Attachment: bug_20857_output2.zip (application/zip, text), 43.20 KiB.
[22 Jan 2007 11:20]
Giuseppe Maxia
innodb status after third run
Attachment: innodb_status_end2.txt (text/plain), 6.00 KiB.
[21 Apr 2007 0:19]
David Sharnoff
innodb status after run with timeout = 2
Attachment: x (application/octet-stream, text), 6.16 KiB.
[14 May 2007 23:52]
David Sharnoff
output from "show innodb status" while deadlocked and waiting.
Attachment: innodb-status.txt (text/plain), 3.84 KiB.
