| Bug #66402 | Thread locks itself out with semaphore (crash) | ||
|---|---|---|---|
| Submitted: | 15 Aug 2012 16:14 | Modified: | 28 Mar 2014 20:25 |
| Reporter: | Trey Raymond | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
| Version: | 5.5.21-55-log Percona | OS: | Linux |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | crash, Semaphore | ||
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
[15 Aug 2012 16:15]
Trey Raymond
[15 Aug 2012 16:15]
Trey Raymond
global status (lots of spin waits)
Attachment: bruno.sts (application/octet-stream, text), 9.66 KiB.
[15 Aug 2012 16:15]
Trey Raymond
global variables
Attachment: bruno.var (application/octet-stream, text), 10.56 KiB.
[26 Feb 2014 9:31]
Serge Rivest
Massive pile up of threads that self-lock
Attachment: innodb-status (1).log.gz (application/x-gzip, text), 2.30 MiB.
