MySQL Bugs: #97808: Truncate table in Master-slave replication

Bug #97808	Truncate table in Master-slave replication
Submitted:	27 Nov 2019 6:20	Modified:	27 Dec 2019 9:12
Reporter:	DBAJJ J	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S2 (Serious)
Version:	5.6	OS:	Any
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	Master-slave, MySQL, replication

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

Master config

Attachment: master.cnf (application/octet-stream, text), 2.59 KiB.

Slave 1

Attachment: SlaveA.cnf (application/octet-stream, text), 2.67 KiB.

Slave 2

Attachment: SlaveB.ini (application/octet-stream, text), 13.83 KiB.