MySQL Bugs: #91096: Binlog dump blocking thread pool group

Bug #91096	Binlog dump blocking thread pool group
Submitted:	31 May 2018 20:35	Modified:	1 Jul 2018 12:29
Reporter:	Hao Xu	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.7.15	OS:	CentOS (CentOS Linux release 7.4.1708 (Core))
Assigned to:		CPU Architecture:	Any
Tags:	Binlogdump, hang, thread pool

Description:
1) The uptime of the problematic boxes are >= 250 days 
2) One of the thread pool group is blocked, processes in this group are in the KILLED status and never release, no response to client 
3) in the blocked thread group, the smallest process id is always binlog dump. 
4) the new processes will be hang if they are assign to the blocked group.
5) the processes in other thread pool groups work fine at the same time. 
6) after kill the binlog dump process, all the KILLED processes will be cleared immediately, DB backs to normal

How to repeat:
N/A

HI,

Thank you for your bug report.

In order that we can process your report, we definitely require further info:

* the output from mysqld --version
* precise description of the hardware on which you run our server
* all the info on how the entire MySQL and its clients are configured ... both config files and arguments
* the output from all three INFORMATION_SCHEMA tables related to our Thread Pool

If you do not feel like exposing this info to the public, please create an SR or send all this info in the private comment.

Thanks in advance.

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".