Bug #44841 | purge thread + rollback hang forever waiting on dict_operation_lock semaphore | ||
---|---|---|---|
Submitted: | 13 May 2009 9:39 | Modified: | 14 Jan 2013 18:23 |
Reporter: | Nickolay Vinogradov | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
Version: | 5.1.34-0, 5.1.43sp1 | OS: | Linux (SUSE Linux Enterprise Server 10 SP2 (x86_64)) |
Assigned to: | Sunny Bains | CPU Architecture: | Any |
Tags: | RW-latch dict0dict.c, X-lock |
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
[13 May 2009 9:45]
Nickolay Vinogradov
[13 May 2009 12:29]
Nickolay Vinogradov
my.cnf
Attachment: my.cnf (application/octet-stream, text), 20.56 KiB.
[13 May 2009 14:34]
Nickolay Vinogradov
Warning and InnoDB Monitor Output(Previous Hang)
Attachment: innodb_monitor_output2.log (text/x-log), 140.53 KiB.
[18 May 2009 17:10]
Nickolay Vinogradov
Innodb monitor output
Attachment: innodb_monitor_output3.txt (text/plain), 62.52 KiB.
[7 Jun 2009 20:00]
Nickolay Vinogradov
Last innodb monitor output
Attachment: innodb.out.333 (application/octet-stream, text), 62.52 KiB.