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

MariaDB Server deadlock

    XMLWordPrintable

Details

    Description

      Many threads in our application hanged up in waiting on response of MariaDB server.
      After waiting more than 10 minutes our application and the the MariaDB server was restarted on a different server.
      A minidump of the MariaDB server was created.

      Attachments

        1. annotated_interesting_stacks.txt
          13 kB
          Vladislav Vaintroub
        4. my.ini
          1 kB
          Michael Graf
        5. my.ini
          1 kB
          Michael Graf
        6. mysqld_exe_190816_130623_all_stacks.txt
          107 kB
          Vladislav Vaintroub
        7. mysqld_exe_190816_130623_uniqstack.txt
          33 kB
          Vladislav Vaintroub
        8. mysqld.err
          25 kB
          Michael Graf
        10. mysqld.exe_190820_all_stacks.txt
          198 kB
          Vladislav Vaintroub
        11. mysqld.exe_190820_uniqstack.txt
          60 kB
          Vladislav Vaintroub
        12. Q100SPW-XYZ-H1.err
          85 kB
          Michael Graf
        13. ThreadsWaitingOnResponseOfMariaDBServer.txt
          119 kB
          Michael Graf
        14. uniqstack.txt
          216 kB
          Vladislav Vaintroub

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-17063 server locks up and is killed after innodb_fatal_semaphore_wait_threshold is reached

          • Major - Major loss of function.
          • Closed

          Activity

            People

              wlad Vladislav Vaintroub
              migra Michael Graf
              Votes:
              0 Vote for this issue
              Watchers:
              7 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.