| Bug #61562 | Replication slows down after network glitch, needs stop/start slave to recover | ||
|---|---|---|---|
| Submitted: | 19 Jun 2011 8:46 | Modified: | 4 Jul 2011 8:38 |
| Reporter: | Kees Jan Koster | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.5.8 | OS: | FreeBSD |
| Assigned to: | 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
[19 Jun 2011 8:47]
Kees Jan Koster
[19 Jun 2011 8:48]
Kees Jan Koster
cron job and cron job output
Attachment: mysql-slave-restart.txt (text/plain), 10.28 KiB.
