| Bug #49399 | BACKUP/RESTORE thread fails to wake up on concurrent BACKUP/RESTORE | ||
|---|---|---|---|
| Submitted: | 3 Dec 2009 13:53 | Modified: | 30 Dec 2009 13:44 |
| Reporter: | Philip Stoev | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Backup | Severity: | S2 (Serious) |
| Version: | 6.0-backup | OS: | Any |
| Assigned to: | Assigned Account | 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
[3 Dec 2009 13:54]
Philip Stoev
[10 Dec 2009 8:26]
Ritheesh Vedire
The Test as described in the Rafal's hypothesis. No hang was observed.
Attachment: bug49399.test (application/octet-stream, text), 1.16 KiB.
[10 Dec 2009 8:28]
Ritheesh Vedire
The result file. Backup got clearly executed even after a different thread,which acquired a shared lock is killed.
Attachment: bug49399.result (application/octet-stream, text), 549 bytes.
