| Bug #68525 | Error "When GTID_NEXT is set to a GTID" ROW based replication | ||
|---|---|---|---|
| Submitted: | 28 Feb 2013 15:32 | Modified: | 7 Sep 2015 17:07 |
| Reporter: | Nogueira Jesus | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S1 (Critical) |
| Version: | 5.6.10, 5.6.11 | OS: | Linux (64 bits) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | GTID_NEXT ROW BASED REPLICATION ERROR WHEN ROTATE LOGS | ||
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
[28 Feb 2013 19:56]
Sveta Smirnova
[28 Feb 2013 19:57]
Sveta Smirnova
master option file, slave uses same option file
Attachment: rpl_bug68525-master.opt (application/octet-stream, text), 267 bytes.
[15 Oct 2013 20:48]
martin fuxa
decoded relay log with comments
Attachment: h7-repl-2243.log (text/x-log), 7.77 KiB.
