summaryrefslogtreecommitdiff
path: root/mysql-test/suite
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2020-06-08 10:28:34 +0300
committerMarko Mäkelä <marko.makela@mariadb.com>2020-06-08 10:35:06 +0300
commitf458b40f66f33521ad3e4f0d4ebcbbcc501c89ed (patch)
tree3c5c2cb6061e2ae7ae4c55f50734170900fcd78d /mysql-test/suite
parente9dbbf112041cd9441ec0eee934e526617eb1213 (diff)
downloadmariadb-git-f458b40f66f33521ad3e4f0d4ebcbbcc501c89ed.tar.gz
MDEV-22827 InnoDB: Failing assertion: purge_sys->n_stop == 0
When MDEV-22769 introduced srv_shutdown_state=SRV_SHUTDOWN_INITIATED in commit efc70da5fd0459ff44153529d13651741cc32bc4 we forgot to adjust a few checks for SRV_SHUTDOWN_NONE. In the initial shutdown step, we are waiting for the background DROP TABLE queue to be processed or discarded. At that time, some background tasks (such as buffer pool resizing or dumping or encryption key rotation) may be terminated, but others must remain running normally. srv_purge_coordinator_suspend(), srv_purge_coordinator_thread(), srv_start_wait_for_purge_to_start(): Treat SRV_SHUTDOWN_NONE and SRV_SHUTDOWN_INITIATED equally.
Diffstat (limited to 'mysql-test/suite')
0 files changed, 0 insertions, 0 deletions