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

MariaDB unresponsive due to long semaphore wait

Details

    Description

      MariaDB was responsive for a long time, queries are in the struck state. Even killing queries is not helping as it is in the killed state for such a long time.

      Forcefully killed mysqld, but post restart issue still persists. These errors are logged in errorlogs

      InnoDB: Warning: a long semaphore wait:
      --Thread 139382773094144 has waited at row0sel.cc line 3056 for 241.00 seconds the semaphore:
      S-lock on RW-latch at 0x7f1224fb6120 '&block->lock'
      a writer (thread id 139382773094144) has reserved it in mode exclusive
      number of readers 0, waiters flag 1, lock_word: 0
      Last time read locked in file row0sel.cc line 3231
      Last time write locked in file /home/buildbot/buildbot/build/storage/xtradb/buf/buf0buf.cc line 4044
      Holder thread 0 file not yet reserved line 0

      --Thread 139365758682880 has waited at lock0lock.cc line 7620 for 0.0000 seconds the semaphore:
      Mutex at 0x7ec298006068 '&lock_sys->mutex', lock var 1
      Last time reserved by thread 139365793367808 in file not yet reserved line 0, waiters flag 1

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          elenst Elena Stepanova added a comment -

          Sukan,

          Are you really running 10.1.10? There have been many fixes since then, including some for InnoDB. By the nature of the problem, it's nearly impossible to say whether this particular one was fixed, but there are some chances.

          Passing to jplindst for his collection of long semaphore waits, just in case.

          elenst Elena Stepanova added a comment - Sukan , Are you really running 10.1.10? There have been many fixes since then, including some for InnoDB. By the nature of the problem, it's nearly impossible to say whether this particular one was fixed, but there are some chances. Passing to jplindst for his collection of long semaphore waits, just in case.
          Sukan Sukan added a comment -

          Yes @Elena. we are running with 10.1.10-MariaDB-log.

          MariaDB [(none)]> select @@version;
          ---------------------

          @@version

          ---------------------

          10.1.10-MariaDB-log

          ---------------------

          Waiting to hear more from @Jan Lindstrom.

          Sukan Sukan added a comment - Yes @Elena. we are running with 10.1.10-MariaDB-log. MariaDB [(none)] > select @@version; --------------------- @@version --------------------- 10.1.10-MariaDB-log --------------------- Waiting to hear more from @Jan Lindstrom.
          jplindst Jan Lindström (Inactive) added a comment -

          Hi, can you provide full unedited error log, my.cnf, output from show processlist when stuck, and attach a debugger and provide output from thread apply all bt ? Note that 10.1.10 is not safe for production.

          jplindst Jan Lindström (Inactive) added a comment - Hi, can you provide full unedited error log, my.cnf, output from show processlist when stuck, and attach a debugger and provide output from thread apply all bt ? Note that 10.1.10 is not safe for production.
          Sukan Sukan added a comment -

          Hi Jan,

          Could you let me know the reason for saying that 10.1.10 is not safe for prod.

          Sukan Sukan added a comment - Hi Jan, Could you let me know the reason for saying that 10.1.10 is not safe for prod.
          jplindst Jan Lindström (Inactive) added a comment -

          https://mariadb.org/mariadb-server-versions-remote-root-code-execution-vulnerability-cve-2016-6662/

          And if you use encryption, there has been a lot of fixes.

          jplindst Jan Lindström (Inactive) added a comment - https://mariadb.org/mariadb-server-versions-remote-root-code-execution-vulnerability-cve-2016-6662/ And if you use encryption, there has been a lot of fixes.
          janlindstrom Jan Lindström added a comment -

          10.1 is EOL.

          janlindstrom Jan Lindström added a comment - 10.1 is EOL.

          People

            jplindst Jan Lindström (Inactive)
            Sukan Sukan
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.