--innodb_purge_threads=1 may result in incomplete purge with innodb_fast_shutdown=0
Bug #1609364 reported by
Laurynas Biveinis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Fix Released
|
Medium
|
Laurynas Biveinis | |||
5.6 |
Invalid
|
Undecided
|
Unassigned | |||
5.7 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
A 5.5-only issue, the main loop of the separate 5.5 purge thread has the following break condition:
/* Check for shutdown and whether we should do purge at all. */
if (srv_force_recovery >= SRV_FORCE_
|| srv_shutdown_state != 0
|| srv_fast_shutdown) {
break;
}
Which means immediate exit on srv_shutdown_state != 0, even if the thread should continue to purge if srv_fast_shutdown == 0.
This is likely the cause of bug 756387. This is an upstream issue but the upstream defaults to --innodb-
description: | updated |
tags: | added: innodb upstream |
To post a comment you must log in.
https:/ /github. com/percona/ percona- server/ pull/769 /github. com/percona/ percona- server/ pull/770 /github. com/percona/ percona- server/ pull/771
https:/
https:/