| Bug #56739 | binary log activation sets server_id implicitly, but replication fails | ||
|---|---|---|---|
| Submitted: | 12 Sep 2010 22:19 | Modified: | 21 Oct 2013 13:04 |
| Reporter: | Giuseppe Maxia | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.1.50 | OS: | Any (Mac OSX, Linux) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | binary logs., replication, server-id | ||
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
