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

InnoDB: Semaphore wait has lasted > 600 second

    XMLWordPrintable

Details

    Description

      After upgrading 10.4.15 to 10.4.17 I experience forced crashes every few days.
      This is zabbix database (like MDEV-24504 ).
      Last crash is from debug build.
      I'll attach full log and backtraces

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-24378 Crashes on Semaphore wait > 600 seconds

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-24504 [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-24275 InnoDB persistent stats analyze forces full scan forcing lock crash

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-25111 Long semaphore wait (> 800 secs), server stops responding

          • Major - Major loss of function.
          • Closed

          Activity

            People

              marko Marko Mäkelä
              marcin.gryszkalis Marcin Gryszkalis
              Votes:
              1 Vote for this issue
              Watchers:
              6 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.