| Bug #25776 | Replication binlog dump crashing mysql | ||
|---|---|---|---|
| Submitted: | 23 Jan 2007 11:21 | Modified: | 15 Feb 2009 12:07 |
| Reporter: | Stéphane CANEL | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S1 (Critical) |
| Version: | 4.1.22 | OS: | Linux (RHEL 4 update 4) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | Replication binlog dump crashing (master) | ||
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
[23 Jan 2007 13:59]
Stéphane CANEL
[7 Mar 2007 9:49]
Stéphane CANEL
binlog after crash (2)
Attachment: Eliot-bdoc-bin.000965 (application/octet-stream, text), 1.27 KiB.
