mirror of
https://github.com/MariaDB/server.git
synced 2025-07-26 21:25:02 +02:00
a8e35a1cc6
Currently it is allowed to set innodb_io_capacity to very large value up to unsigned 8 byte maximum value 18446744073709551615. While calculating the number of pages to flush, we could sometime go beyond innodb_io_capacity. Specifically, MDEV-24369 has introduced a logic for aggressive flushing when dirty page percentage in buffer pool exceeds innodb_max_dirty_pages_pct. So, when innodb_io_capacity is set to very large value and dirty page percentage exceeds the threshold, there is a multiplication overflow in Innodb page cleaner. Fix: We should prevent setting io_capacity to unrealistic values and define a practical limit to it. The patch introduces limits for innodb_io_capacity_max and innodb_io_capacity to the maximum of 4 byte unsigned integer i.e. 4294967295 (2^32-1). For 16k page size this limit translates to 64 TiB/sec write IO speed which looks sufficient. Reviewed by: Marko Mäkelä |
||
|---|---|---|
| .. | ||
| buf0buddy.cc | ||
| buf0buf.cc | ||
| buf0checksum.cc | ||
| buf0dblwr.cc | ||
| buf0dump.cc | ||
| buf0flu.cc | ||
| buf0lru.cc | ||
| buf0rea.cc | ||