diff options
author | Marko Mäkelä <marko.makela@mariadb.com> | 2020-11-25 16:09:47 +0200 |
---|---|---|
committer | Marko Mäkelä <marko.makela@mariadb.com> | 2020-11-25 16:09:47 +0200 |
commit | 7b1252c03d7131754d9503560fe507b33ca1f8b4 (patch) | |
tree | 96bc303f2bca12848ccdc9aae172994506bcd8d6 /config.h.cmake | |
parent | f693b72547e32e5b27e66146003d53fa3a4a67b2 (diff) | |
download | mariadb-git-7b1252c03d7131754d9503560fe507b33ca1f8b4.tar.gz |
MDEV-24278 InnoDB page cleaner keeps waking up on idle server
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.
buf_flush_page_cleaner(): Explicitly note when the page cleaner is idle.
When that happens, use mysql_cond_wait() instead of mysql_cond_timedwait().
buf_flush_insert_into_flush_list(): Wake up the page cleaner if needed.
innodb_max_dirty_pages_pct_update(),
innodb_max_dirty_pages_pct_lwm_update():
Wake up the page cleaner just in case.
Note: buf_flush_ahead(), buf_flush_wait_flushed() and shutdown are
already waking up the page cleaner thread.
Diffstat (limited to 'config.h.cmake')
0 files changed, 0 insertions, 0 deletions