summaryrefslogtreecommitdiff
path: root/storage/innobase/include/sync0rw.ic
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2020-06-02 14:40:51 +0300
committerMarko Mäkelä <marko.makela@mariadb.com>2020-06-02 14:40:51 +0300
commit6df2f2db11bf0a559db54e18315ad37e6a4d5573 (patch)
tree00dcd66bc57c933bd17a399e544935ee251bd4c1 /storage/innobase/include/sync0rw.ic
parent0d6d63e1505bbf9898d46fa641a7a0579a4ae460 (diff)
downloadmariadb-git-6df2f2db11bf0a559db54e18315ad37e6a4d5573.tar.gz
MDEV-21546 main.backup_stages occasionally reports lock wait timeout
With MDEV-16678, InnoDB background tasks (most notably, the purge of committed transaction history) can acquire metadata locks. Because of this, the lock_wait_timeout=0 is too strict and must be relaxed. The test used to fail easily if an extra sleep was added to the end of dict_table_close(), before the MDL release. Now, with lock_wait_timeout=1, the test passes even with an extra 0.1-second sleep added to dict_table_close(). Thanks to Monty for providing this fix.
Diffstat (limited to 'storage/innobase/include/sync0rw.ic')
0 files changed, 0 insertions, 0 deletions