Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-39104

Hang in the test innodb.log_file_size,debug

    XMLWordPrintable

Details

    • Not for Release Notes

    Description

      The InnoDB startup and shutdown were recently optimized and simplified in MDEV-38968 and MDEV-38833. After one of these changes, we have occasional failures of the tests innodb.log_file_size and innodb.log_file_overwrite. Here is an example:

      10.11 3766b0d1ca8555b2963ee9863c88179aae89382c

      innodb.log_file_size '4k,debug'          w1 [ fail ]
              Test ended at 2026-03-13 14:04:20
      CURRENT_TEST: innodb.log_file_size
      mysqltest: In included file "./include/wait_until_connected_again.inc": 
      included from ./include/start_mysqld.inc at line 49:
      included from ./include/restart_mysqld.inc at line 11:
      included from /home/buildbot/src/mysql-test/suite/innodb/t/log_file_size.test at line 117:
      At line 44: Server failed to restart
      

      In the test we find the following:

      mysql-test/suite/innodb/t/log_file_size.test

      114
      if ($have_debug) {
      115
      --let $restart_parameters= --debug=d,innodb_log_abort_1
      116
      --source include/restart_mysqld.inc
      117
      --error ER_UNKNOWN_STORAGE_ENGINE
      118
      SELECT * FROM t1;
      119
      let SEARCH_PATTERN= InnoDB: Starting crash recovery from checkpoint LSN=.*;
      120
      --source include/search_pattern_in_file.inc
      121
      }
      

      Inside the archive of the corresponding logs we find the following:

      logs/normal/1/log/mysqld.1.err

      7021
      $ /home/buildbot/bld/sql/mariadbd --defaults-group-suffix=.1 --defaults-file=/dev/shm/normal/1/my.cnf --log-output=file --innodb-page-size=4K --skip-innodb-read-only-compressed --enable-gdb --innodb --innodb-cmpmem --innodb-cmp-per-index --innodb-trx --innodb-locks --innodb-lock-waits --innodb-metrics --innodb-buffer-pool-stats --innodb-buffer-page --innodb-buffer-page-lru --innodb-sys-columns --innodb-sys-fields --innodb-sys-foreign --innodb-sys-foreign-cols --innodb-sys-indexes --innodb-sys-tables --innodb-sys-virtual --debug=d,innodb_log_abort_1 --core-file --loose-debug-sync-timeout=300
      7022
      2026-03-13 13:55:46 0 [Warning] Could not increase number of max_open_files to more than 1024 (request: 32278)
      7023
      2026-03-13 13:55:46 0 [Warning] Changed limits: max_open_files: 1024  max_connections: 151 (was 151)  table_cache: 421 (was 2000)
      7024
      2026-03-13 13:55:46 0 [Note] Starting MariaDB 10.11.17-MariaDB-asan-debug-log source revision 3766b0d1ca8555b2963ee9863c88179aae89382c server_uid NSZk9kJ5CMXpj7y5cH9KHsTrMF4= as process 212381
      7025
      2026-03-13 13:55:46 0 [Note] Plugin 'partition' is disabled.
      7026
      2026-03-13 13:55:46 0 [Note] Plugin 'SEQUENCE' is disabled.
      7027
      2026-03-13 13:55:46 0 [Note] InnoDB: innodb_page_size=4096
      7028
      2026-03-13 13:55:46 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
      7029
      2026-03-13 13:55:46 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
      7030
      2026-03-13 13:55:46 0 [Note] InnoDB: Number of transaction pools: 1
      7031
      2026-03-13 13:55:46 0 [Note] InnoDB: Using AVX512 instructions
      7032
      2026-03-13 13:55:46 0 [Warning] mariadbd: io_uring_queue_init() failed with EPERM: sysctl kernel.io_uring_disabled has the value 2, or 1 and the user of the process is not a member of sysctl kernel.io_uring_group. (see man 2 io_uring_setup).
      7033
      create_uring failed: falling back to libaio
      7034
      2026-03-13 13:55:46 0 [Note] InnoDB: Using Linux native AIO
      7035
      2026-03-13 13:55:46 0 [Note] InnoDB: innodb_buffer_pool_size_max=8388608m, innodb_buffer_pool_size=8m
      7036
      2026-03-13 13:55:46 0 [Note] InnoDB: Completed initialization of buffer pool
      7037
      2026-03-13 13:55:46 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=67466
      7038
      2026-03-13 13:55:46 0 [Note] InnoDB: End of log at LSN=72006
      7039
      2026-03-13 13:55:46 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 14 row operations to undo
      7040
      2026-03-13 13:55:46 0 [Note] InnoDB: Trx id counter is 43
      7041
      2026-03-13 13:55:46 0 [Note] InnoDB: To recover: 14 pages
      7042
      2026-03-13 13:55:46 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1535] with error Generic error
      7043
      2026-03-13 13:55:46 0 [Note] InnoDB: Starting shutdown...
      7044
      CURRENT_TEST: innodb.log_file_size
      7045
      $ /home/buildbot/bld/sql/mariadbd --defaults-group-suffix=.1 --defaults-file=/dev/shm/normal/1/my.cnf --log-output=file --innodb-page-size=4K --skip-innodb-read-only-compressed --enable-gdb --innodb --innodb-cmpmem --innodb-cmp-per-index --innodb-trx --innodb-locks --innodb-lock-waits --innodb-metrics --innodb-buffer-pool-stats --innodb-buffer-page --innodb-buffer-page-lru --innodb-sys-columns --innodb-sys-fields --innodb-sys-foreign --innodb-sys-foreign-cols --innodb-sys-indexes --innodb-sys-tables --innodb-sys-virtual --core-file --loose-debug-sync-timeout=300
      7046
      2026-03-13 14:04:21 0 [Warning] Could not increase number of max_open_files to more than 1024 (request: 32278)
      

      The InnoDB shutdown actually hung after the fault injection point innodb_log_abort_1 had been tripped.

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              Marko Mäkelä Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.