Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5.1
Description
With MDEV-16678, InnoDB background tasks (most notably, the purge of committed transaction history) can acquire metadata locks. This seems to explain recent failures of the test main.backup_stages in 10.5:
10.5 ce41a9075ad63e5388045943b80f69b7 |
CURRENT_TEST: main.backup_stages
|
mysqltest: At line 177: query 'ALTER TABLE t_permanent_innodb ADD COLUMN col3 INT' failed: 1205: Lock wait timeout exceeded; try restarting transaction
|
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-jessie-x86/builds/7887
10.5 44be8652c567ccaa0067830fa327cbff |
CURRENT_TEST: main.backup_stages
|
mysqltest: At line 145: query 'ALTER TABLE t_permanent_innodb ADD COLUMN col2 INT' failed: 1205: Lock wait timeout exceeded; try restarting transaction
|
http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64-debug/builds/3179
I encountered the first failure (test line 177) locally.
Attachments
Issue Links
- is caused by
-
MDEV-16678 Use MDL for innodb background threads instead of dict_operation_lock
- Closed