Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5
Description
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.
Attachments
Issue Links
- causes
-
MDEV-24369 Page cleaner sleeps indefinitely despite innodb_max_dirty_pages_pct_lwm being exceeded
- Closed
-
MDEV-26819 SET GLOBAL innodb_max_dirty_pages_pct=0 occasionally fails to trigger writes
- Closed
-
MDEV-27416 InnoDB hang in buf_flush_wait_flushed(), on log checkpoint
- Closed
- relates to
-
MDEV-24280 InnoDB triggers too many independent periodic tasks
- Closed
-
MDEV-27461 Server hangs when the bufferpool is shrunk to 8M and innodb_page_size=64K
- 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
-
MDEV-26784 [Warning] InnoDB: Difficult to find free blocks in the buffer pool
- Closed