| Bug #42784 | archive tables cause 100% cpu usage and hang in show table status | ||
|---|---|---|---|
| Submitted: | 12 Feb 2009 10:05 | Modified: | 6 Dec 2011 0:51 |
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Archive storage engine | Severity: | S3 (Non-critical) |
| Version: | 5.0.88-debug, 5.1.31-debug, 5.1.42-debug | OS: | Any (Windows, Mac OS X) |
| Assigned to: | Sergey Vojtovich | CPU Architecture: | Any |
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
[9 Dec 2009 16:07]
Shane Bester
[10 Dec 2009 15:00]
Shane Bester
more problems/details about original bug47012.c testcase.
Attachment: bug47012_5.1.43-debug_multiple_problems.txt (text/plain), 11.56 KiB.
[21 Sep 2011 12:17]
Shane Bester
here is a stress test. still causes valgrind errors on trunk and 2GB mallocs on 5.5.17
Attachment: bug47012.c (text/plain), 146.64 KiB.
