Uploaded image for project: 'MariaDB Foundation Development'
  1. MariaDB Foundation Development
  2. MDBF-358

buildbot: raise memlock limits so uring is actually tested in containers

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • N/A
    • N/A
    • Buildbot
    • 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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29610 uring tmpfs InnoDB: IO Error: 125 during async write of X bytes, for file Y, returned 0

          • Major - Major loss of function.
          • Stalled

          Activity

            People

              vladbogo Vlad Bogolin
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0d
                  0d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 3h
                  3h