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

InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch crash

    XMLWordPrintable

Details

    • Bug
    • Status: Needs Feedback (View Workflow)
    • Critical
    • Resolution: Unresolved
    • 10.11.5
    • None
    • None
    • Alma linux

    Description

      Hi Team,
      Our primary cluster node was crashed and we have found the below entries in the mariadb log. Please check and help me with this

      10.11.5 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c

      2024-03-09  2:40:05 0 [Warning] InnoDB: Long wait (150 seconds) for dict_sys.latch
      2024-03-09  2:42:35 0 [Warning] InnoDB: Long wait (300 seconds) for dict_sys.latch
      2024-03-09  2:45:05 0 [Warning] InnoDB: Long wait (450 seconds) for dict_sys.latch
      2024-03-09  2:47:35 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
      240309  2:47:35 [ERROR] mysqld got signal 6 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
       
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed,
      something is definitely wrong and this may fail.
       
      Server version: 10.11.5-MariaDB source revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=612
      max_threads=653
      thread_count=645
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1569318 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x0 thread_stack 0x49000
      2024-03-09  2:47:37 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT2.41738S), skipping check
      /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x558cdfbf86ce]
      /usr/sbin/mariadbd(handle_fatal_signal+0x478)[0x558cdf6d5028]
      2024-03-09  2:49:19 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.82485S), skipping check
      /lib64/libc.so.6(+0x54db0)[0x7ff454854db0]
      /lib64/libc.so.6(+0xa154c)[0x7ff4548a154c]
      /lib64/libc.so.6(raise+0x16)[0x7ff454854d06]
      /lib64/libc.so.6(abort+0xd3)[0x7ff4548287f3]
      /usr/sbin/mariadbd(+0x69b55f)[0x558cdf30455f]
      /usr/sbin/mariadbd(+0x691d52)[0x558cdf2fad52]
      /usr/sbin/mariadbd(_ZN5tpool19thread_pool_generic13timer_generic7executeEPv+0x40)[0x558cdfb8fb80]
      /usr/sbin/mariadbd(_ZN5tpool4task7executeEv+0x32)[0x558cdfb905e2]
      /usr/sbin/mariadbd(_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x4f)[0x558cdfb8e74f]
      2024-03-09  2:52:55 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.74234S), skipping check
      /lib64/libstdc++.so.6(+0xdb924)[0x7ff454cdb924]
      2024-03-09  2:54:46 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.68565S), skipping check
      /lib64/libc.so.6(+0x9f802)[0x7ff45489f802]
      /lib64/libc.so.6(+0x3f450)[0x7ff45483f450]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /data/mysql
      Resource Limits:
      Limit                     Soft Limit           Hard Limit           Units
      Max cpu time              unlimited            unlimited            seconds
      Max file size             unlimited            unlimited            bytes
      Max data size             unlimited            unlimited            bytes
      Max stack size            8388608              unlimited            bytes
      Max core file size        0                    unlimited            bytes
      Max resident set          unlimited            unlimited            bytes
      Max processes             1028764              1028764              processes
      Max open files            32768                32768                files
      Max locked memory         8388608              8388608              bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       1028764              1028764              signals
      Max msgqueue size         819200               819200               bytes
      Max nice priority         0                    0
      Max realtime priority     0                    0
      Max realtime timeout      unlimited            unlimited            us
      Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h
       
      Kernel version: Linux version 5.14.0-284.11.1.el9_2.x86_64 (mockbuild@x64-builder01.almalinux.org) (gcc (GCC) 11.3.1 20221121 (Red Hat 11.3.1-4), GNU ld version 2.35.2-37.el9) #1 SMP PREEMPT_DYNAMIC Tue May 9 05:49:00 EDT 2023
       
      2024-03-09  2:55:35 0 [Note] Starting MariaDB 10.11.5-MariaDB source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 765634
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              prabha Prabha
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.