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

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

          Activity

            danblack Daniel Black created issue -
            danblack Daniel Black made changes -
            Field Original Value New Value
            Worklog Id 96204 [ 96204 ]
            Remaining Estimate 0d [ 0 ]
            Time Spent 0.5h [ 1800 ]
            danblack Daniel Black made changes -
            Worklog Id 96235 [ 96235 ]
            Time Spent 0.5h [ 1800 ] 1h [ 3600 ]
            danblack Daniel Black made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            danblack Daniel Black made changes -
            Component/s Buildbot [ 18503 ]
            danblack Daniel Black made changes -
            Summary buildbot: enable uring in containers buildbot: raise memlock limits so uring is actually tested in containers
            danblack Daniel Black made changes -
            faust Faustin Lammler made changes -
            Assignee Faustin Lammler [ faust ] Vlad Bogolin [ vladbogo ]
            vladbogo Vlad Bogolin made changes -
            Fix Version/s N/A [ 27305 ]
            Affects Version/s N/A [ 27305 ]
            Description
            {noformat:title=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
            {noformat}

            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.
            {noformat:title=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
            {noformat}

            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.
            Original Estimate 0d [ 0 ]
            vladbogo Vlad Bogolin made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            vladbogo Vlad Bogolin made changes -
            Worklog Id 103161 [ 103161 ]
            Time Spent 1h [ 3600 ] 3h [ 10800 ]
            vladbogo Vlad Bogolin made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            julien.fritsch Julien Fritsch made changes -
            Workflow MariaDB v4 [ 163668 ] MariaDB Foundation v1 [ 188586 ]

            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