Skip to:
**Reported in Launchpad by Laurynas Biveinis last update 03-08-2016 17:17:03
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_NO_BACKGROUND
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-purge-threads=0 whereas the PS default is 1.
**Comment from Launchpad by: Laurynas Biveinis on: 03-08-2016 17:16:53
https://github.com/percona/percona-server/pull/769https://github.com/percona/percona-server/pull/770https://github.com/percona/percona-server/pull/771
**Reported in Launchpad by Laurynas Biveinis last update 03-08-2016 17:17:03
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_NO_BACKGROUND
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-purge-threads=0 whereas the PS default is 1.