| Bug #89987 | super_read_only with master_info_repository=TABLE breaks replication on restart | ||
|---|---|---|---|
| Submitted: | 9 Mar 2018 13:00 | Modified: | 28 Mar 2019 16:24 |
| Reporter: | Clemens Weiß | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.7.21 | OS: | Ubuntu (16.04) |
| Assigned to: | CPU Architecture: | x86 (amd64) | |
| Tags: | master_info_repository, replication, super_read_only | ||
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
[12 Mar 2018 8:36]
Umesh Shastry
