MySQL Bugs: #89585: Errcode: 24 - Too many open files on replication side

Bug #89585	Errcode: 24 - Too many open files on replication side
Submitted:	8 Feb 2018 8:59	Modified:	20 Apr 2018 7:35
Reporter:	HengWay Ong	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S1 (Critical)
Version:	5.6.39-log	OS:	Windows
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	replication

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

tmp_dir that accumulate 20k of temporary file

Attachment: mysql_error.png (image/png, text), 67.46 KiB.

I checked on master binlog, found a lot of drop temporary statement like above which generated by server.

Attachment: mysql_binlog.jpeg (image/jpeg, text), 30.79 KiB.

This is the create and drop temp that we extract from binlog, look like the count is equal

Attachment: binlog.png (image/png, text), 2.72 MiB.

sorry for miss the slave_open_temporary_table, the value not so huge now, because we regularly restart mysql to prevent issue

Attachment: mysql_slave_open_temporary_tables.jpeg (image/jpeg, text), 10.00 KiB.

Attachment is the binlog that extract. Please help check. thank you

Attachment: binlog_for_tmp_table.txt (text/plain), 190.98 KiB.

this is the slave_open_temporary_tables for one of the replication instance that running for almost 5 days.

Attachment: mysql_1.png (image/png, text), 84.04 KiB.

This is the result from mysqladmin status. Hope this data will help

Attachment: mysql_2.png (image/png, text), 14.00 KiB.