-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.2, 10.3, 10.4, 10.5
-
Fix Version/s: 10.5.9
-
Component/s: Storage Engine - InnoDB
-
Labels:
The purpose of the InnoDB page cleaner subsystem is to write out modified pages from the buffer pool to data files. When the innodb_max_dirty_pages_pct_lwm is not exceeded or innodb_adaptive_flushing=ON decides not to write out anything, the page cleaner should keep sleeping indefinitely until the state of the system changes: a dirty page is added to the buffer pool such that the page cleaner would no longer be idle.
- causes
-
MDEV-24369 Page cleaner sleeps indefinitely despite innodb_max_dirty_pages_pct_lwm being exceeded
-
- Closed
-
- relates to
-
MDEV-24280 InnoDB triggers too many independent periodic tasks
-
- Closed
-
-
MDEV-23399 10.5 performance regression with IO-bound tpcc
-
- Closed
-
-
MDEV-24270 Misuse of io_getevents() causes wake-ups at least twice per second
-
- Closed
-
-
MDEV-24917 Flushing starts only when 90% (srv_max_buf_pool_modified_pct) pages are modified
-
- Closed
-