SIGTERM kills server instead of shutdown w/ threadpool, spurious mysqld_safe server restarts
Bug #1537554 reported by
Josip Deanovic
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Invalid
|
Undecided
|
Unassigned | |||
5.7 |
Fix Released
|
High
|
Laurynas Biveinis |
Bug Description
OS: Centos 6.7 x86_64
Percona server version: 5.7.10-
When the option "thread_handling = pool-of-threads" is added to the "[mysqld]" section of the /etc/my.cnf config file the mysql service cannot be gracefully shutdown using corresponding init script.
There is a similar but very old bug report for Percona XtraDB Cluster:
https:/
However it seems that the bug still exist in the Percona Server 5.7.10-1rc1.
tags: |
added: threadpool removed: pool-of-thread |
Changed in percona-server: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: regression |
summary: |
- Fail to gracefully shutdown when using pool-of-threads + SIGTERM kills server instead of shutdown w/ threadpool, spurious + mysqld_safe server restarts |
To post a comment you must log in.
I have just noticed that the bug does not exist with 5.6.27- rel76.0. el6.x86_ 64 (Centos 6.7 x86_64).