mirror of
https://github.com/MariaDB/server.git
synced 2025-04-05 23:05:34 +02:00
77bebe9eb0
During regular iteration the page cleaner does flush from flush list with some flush target and then goes for generating free pages from LRU tail. When asynchronous flush is triggered i.e. when 7/8 th of the LSN margin is filled in the redo log, the flush target for flush list is set to innodb_io_capacity_max. If it could flush all, the flush bandwidth for LRU flush is currently set to zero. If the LRU tail has dirty pages, page cleaner ends up freeing no pages in one iteration. The scenario could repeat across multiple iterations till async flush target is reached. During this time the DB system is starved of free pages resulting in apparent stall and in some cases dict_sys latch fatal error. Fix: In page cleaner iteration, before LRU flush, ensure we provide enough flush limit so that freeing pages is no blocked by dirty pages in LRU tail. Log IO and flush state if double write flush wait is long. Reviewed by: Marko Mäkelä |
||
|---|---|---|
| .. | ||
| dict0boot.cc | ||
| dict0crea.cc | ||
| dict0defrag_bg.cc | ||
| dict0dict.cc | ||
| dict0load.cc | ||
| dict0mem.cc | ||
| dict0stats.cc | ||
| dict0stats_bg.cc | ||
| drop.cc | ||