Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
Description
The tests innodb.undo_truncate and innodb.full_crc32_import are occasionally failing due to not all transactions having been purged. This is deterministically repeatable on a slow VM when running an ASAN-instrumented executable.
The reason for this is that the purge worker threads are unnecessarily issuing repeated lookups for tables that have been dropped, rebuilt or discarded. The threads should remember the latest failed lookup, so that unnecessary contention on the InnoDB dict_sys->mutex and dict_operation_lock and the buffer pool pages for SYS_TABLES can be avoided.
Attachments
Issue Links
- relates to
-
MDEV-11802 innodb.innodb_bug14676111 fails in buildbot due to InnoDB purge failing to start when there is work to do
- Closed
-
MDEV-17745 innodb.innodb_stats_persistent failed in buildbot with wrong result
- Closed