Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
N/A
-
None
Description
|
from worker p9-db-bbw1-docker-debian-sid(https://ci.mariadb.org/23085/logs/ppc64le-debian-sid/mysqld.1.err.3) |
2022-03-09 4:12:07 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 1
|
2022-03-09 4:12:07 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
|
So errno 1 is a EPERM. Other workers have ENOSYS indicating an unsupported kernel.
Without uring enable on a variety of architectures, there isn't sufficient testing of innodb's default mode of writing.
Attachments
Issue Links
- relates to
-
-
- Stalled
-
Activity
FYI (and as already discussed) liburing-devel is not available in rhel9, see also:
https://github.com/MariaDB/mariadb.org-tools/pull/160
Please update the memlock limits. Spent a long time working out why MDEV-29610 isn't affecting bb.org builders.
And we're delivering significant functionality (10.6+ liburing), that is complicated, and untested, to delivering this packaged to users.
Just 1M of locked memory as the default memlock limit per container.
This is needed in all hosts running a kernel < 5.12.
Assigned to vladbogo since it's better to be managed at BB level. Re-assign to me if we want to manage this at docker daemon level.
Not really. It was quite painful to go through and find this one warning (I'm not sure I found any successes)
Best I can think of at the moment is to take a test from https://github.com/axboe/liburing/tree/master/test, suggestion read-write.c, compile against the worker liburing (so don't pull the latest feature tests) into the bb workers, and run it on some pre-step in worker jobs. Like
MDBF-386it can be a worker information finding stage.I don't think properties are a cross reference searchable item but it should be possible to extend it that way.