MySQL Bugs: #88720: Inconsistent and unsafe FLUSH behavior in terms of replication

Bug #88720	Inconsistent and unsafe FLUSH behavior in terms of replication
Submitted:	30 Nov 2017 14:52	Modified:	1 Dec 2017 7:11
Reporter:	Przemyslaw Malkowski	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	5.6, 5.7, 8.0.3, 5.6.38, 5.7.20	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	flush

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

File:	Maximum allowed size is 50MB.
Description:
Privacy:

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

test case for MTR

Attachment: rpl_bug88720.test (application/octet-stream, text), 441 bytes.

Option file for master, copy same file for slave

Attachment: rpl_bug88720-master.opt (application/octet-stream, text), 72 bytes.