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

InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch

    XMLWordPrintable

Details

    Description

      The server hangs with a lot of queries in 'Killed' status. The main culprit to the hang seems to be a massive update on a wp_options (wordpress) table. This in itself is not odd.

      What is weird is that MariaDB stops accepting new queries and when the max_connection limit is reach it's restarted. The restart does not work, ends up crashing with error code 6. No core dump dumped as of yet, but I did manage to produce stack traces for all threads (attachment).

      [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/
      240623  8:17:35 [ERROR] mysqld got signal 6 ;
      Sorry, we probably made a mistake, and this is a bug.
       
      Your assistance in bug reporting will enable us to fix this for the next release.
      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.6.18-MariaDB-cll-lve source revision: 887bb3f73555ff8a50138a580ca8308b9b5c069c
      key_buffer_size=402653184
      read_buffer_size=2097152
      max_used_connections=801
      max_threads=802
      thread_count=802
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3699409 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
      /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55fdf610648e]
      mysys/stacktrace.c:216(my_print_stacktrace)[0x55fdf5be1d45]
      /lib64/libpthread.so.0(+0x12d20)[0x7f0ff4915d20]
      /lib64/libc.so.6(gsignal+0x10f)[0x7f0ff3c6052f]
      /lib64/libc.so.6(abort+0x127)[0x7f0ff3c33e65]
      /usr/sbin/mariadbd(+0x678245)[0x55fdf5883245]
      ut/ut0ut.cc:476(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x55fdf587bcdc]
      srv/srv0srv.cc:1233(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x55fdf609a1c8]
      tpool/tpool_generic.cc:346(tpool::thread_pool_generic::timer_generic::execute(void*))[0x55fdf609af0b]
      tpool/task.cc:38(tpool::task::execute())[0x55fdf6098a7f]
      /lib64/libstdc++.so.6(+0xc2b23)[0x7f0ff442cb23]
      /lib64/libpthread.so.0(+0x81ca)[0x7f0ff490b1ca]
      /lib64/libc.so.6(clone+0x43)[0x7f0ff3c4b8d3]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /var/lib/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        unlimited            unlimited            bytes
      Max resident set          unlimited            unlimited            bytes
      Max processes             642336               642336               processes
      Max open files            80000                80000                files
      Max locked memory         65536                65536                bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       642336               642336               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 %e
      

      Attachments

        1. output.log.anon.gz
          236 kB
          Josef Johansson
        2. stacktrace.log
          120 kB
          Josef Johansson

        Issue Links

          Activity

            People

              debarun Debarun Banerjee
              isodude Josef Johansson
              Votes:
              1 Vote for this issue
              Watchers:
              5 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.