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

10.6.12 regression - InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch

    XMLWordPrintable

Details

    Description

      I have transferred this bug from the Ubuntu Bug Tracker:
      https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/2008718

      Ubuntu-Release: (ubuntu-jammy, 22.04, x86_64/amd64; Kernel: 5.15.0-60-generic)
      Affected Package: mariadb-server-10.6 = 10.6.12-0ubuntu0.22.04.1

      It looks like the most recent update to mariadb-server-10.6 (https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/2006882) may have introduced a regression causing lockups as a result of work completed under one of the following:

      MDEV-24911 Missing warning before [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.mutex - Jira

      MDEV-24258 Merge dict_sys.mutex into dict_sys.latch - Jira

      MDEV-26827 Make page flushing even faster - Jira

      We have a large zabbix installation with >398GB history_uint table and ever since this upgrade the mariadb server has been locking up within 2-12 hours with the following error:

      [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch

      Downgrade to previous package version 10.6.11 or 10.6.7 resolves the lockup and our platform remains stable.

      I have not been able to get a proper crash-dump as the mariadb-server does not crash, it simply hangs – and sometimes the watchdog auto-restarts it (though not for several hours).

      Attachments

        Activity

          People

            marko Marko Mäkelä
            jameno123 James Reno
            Votes:
            0 Vote for this issue
            Watchers:
            5 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.