mirror of
https://github.com/MariaDB/server.git
synced 2025-09-29 12:29:12 +02:00
ba9e8ebdbe
Where io_setup fails, this is a serious issue, normally because of the lack of fs.aio-max-nr configured in the kernel. We adjust the error message to be a Warning, because like "native AIO failed: falling back to innodb_use_native_aio=OFF", its user actionable. A default configuation of the server and indeed raising innodb_write_io_threads and innodb_read_io_threads couldn't exceed the default fs.aio-max-nr value. If a user is constructing multipe instances of MariaDB that exceed this value then they should be seeing the warning and taking action. There are CI environments, as Otto points on on Launchpad, that have insufficient fs.aio-max-nr configure to run mtr in parallel. This however a genuine distro problem and to resolve. For us, and our developers, we'd rather see the warning so we can fix CI and dev instances that are insufficiently configured. The io_setup man page as a very short but descript set of causes for the io_setup failures. Its safer to refer to this, now with a strerror description rather than a number. The mtr suppressions are removed because a while ago when the errors where moved out of InnoDB and recently the server could never generate a warning of these forms. |
||
|---|---|---|
| .. | ||
| aio_libaio.cc | ||
| aio_liburing.cc | ||
| aio_linux.cc | ||
| aio_simulated.cc | ||
| aio_win.cc | ||
| CMakeLists.txt | ||
| task.cc | ||
| task_group.cc | ||
| tpool.h | ||
| tpool_generic.cc | ||
| tpool_structs.h | ||
| tpool_win.cc | ||
| wait_notification.cc | ||