MySQL Bugs: #87485: Bulk insert query hang the MySQL server.

Bug #87485	Bulk insert query hang the MySQL server.
Submitted:	21 Aug 2017 5:23	Modified:	21 Sep 2017 8:17
Reporter:	Md Arshad Ali	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: DML	Severity:	S1 (Critical)
Version:	MySQL 5.7.9	OS:	CentOS (Cent OS 6.8)
Assigned to:		CPU Architecture:	Any

Description:
Hi Team,

MySQL service hangs when bulk insert query execution start. We are trying to insert around 2 MB or higher data around 20 thousands rows or higher in one bulk insert query in a busy server having connections more than 600. Same issue occur when we use mysqldump exe to move tables from one to another servers and target server get hang or stuck till complete dump. 

We can not connect MySQL server during after such execution and for resolution required server restart. So, you are requested to check and suggest the feasible solution as this is stopper.

Below are the details for your reference. Please let me know if required further details if any. 

OS : CentOS 6.8
MySQL Version : 5.7.9
RAM : 96 GB
Engine : INNODB
innodb_buffer_pool_size=58 GB
innodb_buffer_pool_instances=16
innodb_thread_concurrency=8
max_allowed_packet=512 MB

Thanks in advance.

How to repeat:
This can be repeat for both cases separately as follows.

1. Need to create bulk insert around 2 MB data and more than 20 thousands rows for 15-20 columns at least. 

2. Dump the tables from one server to another server using mysqldump exe having record counts approx 1-5 lac. (To check the performance may be execute parallel dump of 3 to 4 tables at a time)

Thank you for taking the time to report a problem.  Unfortunately you
are not using a current version of the product you reported a problem
with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/. Re-open this bug when
tested against the current version 5.7.19.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".