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

InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.3.16
    • N/A
    • MariaDB Version: 10.3.16
      system: centos7 (3.10.0-123.20.1.el7.x86_64)
      cpu: 4 cores or 8 cores
      hardware: Alibaba Clould ECS

    Description

      “--Thread 140014490990336 has waited at srv0srv.cc line 915 for 921.00 seconds the semaphore:
      Mutex at 0x7f5852701310, Mutex SRV_SYS created srv0srv.cc:1020, lock var 2”

      Our MariaDB server often restart due to the lock. And it happened even every hour after upgrading the CPU from 4 cores to 8 cores.

      We guess that has something to do with adaptive hash index. Bug it didn't work after set innodb_adaptive_hash_index=0.

      We have no idea. Can we solve this problem by upgrade to a newer version?

      Environment->
      MariaDB Version: 10.3.16
      system: centos7 (3.10.0-123.20.1.el7.x86_64)
      cpu: 4 cores or 8 cores
      hardware: Alibaba Clould ECS

      Attachments

        1. 4C.txt
          80 kB
        2. 8C.txt
          79 kB
        3. server.cnf
          2 kB

        Activity

          People

            marko Marko Mäkelä
            blade08 chencheng
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.