| Bug #26201 | Replication broke on packet size, but show slave status does not indicate this | ||
|---|---|---|---|
| Submitted: | 8 Feb 2007 22:25 | Modified: | 31 May 2007 20:47 |
| Reporter: | Arjen Lentz | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.0, 4.1 BK, 5.1 BK | OS: | Any (any) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | bfsm_2007_02_15, max_allowed_packet, replication, slave status | ||
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 Feb 2007 11:45]
Sveta Smirnova
[9 Feb 2007 11:45]
Sveta Smirnova
data file
Attachment: bug26201.dat (application/octet-stream, text), 2.46 KiB.
[9 Feb 2007 11:46]
Sveta Smirnova
master options file
Attachment: rpl_bug26201-master.opt (application/octet-stream, text), 26 bytes.
[9 Feb 2007 11:46]
Sveta Smirnova
slave options file
Attachment: rpl_bug26201-slave.opt (application/octet-stream, text), 26 bytes.
