Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.12, 10.3.3
-
None
-
linux, ramfs
Description
When running tests with plenty of DDL with datadir on RamFS after upgrade from 10.2.11 to 10.2.12 the following errors occur repeatedly:
[ERROR] InnoDB: Cannot save table statistics for table `some_dir`.`some_table`: Lock wait timeout
then followed by long semaphore wait warnings on the innodb data dictionary mutex:
Jan 5 11:54:11 bamber-02 mysqld: 2018-01-05 11:54:11 140564011710208 [Warning] InnoDB: A long semaphore wait:
|
Jan 5 11:54:11 bamber-02 mysqld: --Thread 140563682322176 has waited at ha_innodb.cc line 13396 for 241.00 seconds the semaphore:
|
Jan 5 11:54:11 bamber-02 mysqld: X-lock on RW-latch at 0x555673f891c0 created in file dict0dict.cc line 1107
|
Jan 5 11:54:11 bamber-02 mysqld: a writer (thread id 140563590076160) has reserved it in mode exclusive
|
Jan 5 11:54:11 bamber-02 mysqld: number of readers 0, waiters flag 1, lock_word: 0
|
Jan 5 11:54:11 bamber-02 mysqld: Last time read locked in file not yet reserved line 0
|
Jan 5 11:54:11 bamber-02 mysqld: Last time write locked in file ha_innodb.cc line 13396
|
Jan 5 11:54:11 bamber-02 mysqld: 2018-01-05 11:54:11 140564011710208 [Warning] InnoDB: A long semaphore wait:
|
and finally lots of
[ERROR] InnoDB: Cannot save table statistics for table `tmp_1e865f785ceff316`.`access_log`: Operation interrupted
after mysqld shutdown was requested
Attachments
Issue Links
- is caused by
-
MDEV-14511 Use fewer transactions for updating InnoDB persistent statistics
- Closed
- relates to
-
MDEV-15020 Server hangs due to InnoDB persistent statistics or innodb_stats_auto_recalc
- Closed