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

Assertion `wsrep::this_thread::get_id() == owning_thread_id_' failed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 10.4.13
    • Fix Version/s: 10.4.14, 10.5.5
    • Component/s: Galera
    • Labels:
      None

      Description

      The following assertion failure happened:

      mysqld: /home/buildbot/buildbot/build/wsrep-lib/src/client_state.cpp:804: void wsrep::client_state::state(wsrep::unique_lock<wsrep::mutex>&, wsrep::client_state::state): Assertion `wsrep::this_thread::get_id() == owning_thread_id_' failed.
      200711  5:57:32 [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.4.13-MariaDB-log
      key_buffer_size=33554432
      read_buffer_size=2097152
      max_used_connections=161
      max_threads=4011
      thread_count=83
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 41204404 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f03c00008c8
      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 = 0x7f05053f7e40 thread_stack 0x49000
      /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x55851ff46e2e]
      /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x30f)[0x55851f957b3f]
      /lib64/libpthread.so.0(+0xf600)[0x7f1881f00600]
      /lib64/libc.so.6(gsignal+0x37)[0x7f1880c8e3a7]
      /lib64/libc.so.6(abort+0x148)[0x7f1880c8fa98]
      /lib64/libc.so.6(+0x2f1c6)[0x7f1880c871c6]
      /lib64/libc.so.6(+0x2f272)[0x7f1880c87272]
      /usr/local/mysql/bin/mysqld(_ZN5wsrep12client_state5stateERNS_11unique_lockINS_5mutexEEENS0_5stateE+0x145)[0x55851ffda515]
      /usr/local/mysql/bin/mysqld(_ZN5wsrep12client_state5closeEv+0x42)[0x55851ffda722]
      /usr/local/mysql/bin/mysqld(_Z14end_connectionP3THD+0x134)[0x55851f8383f4]
      /usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x234)[0x55851f838cc4]
      /usr/local/mysql/bin/mysqld(handle_one_connection+0x3d)[0x55851f838d6d]
      /usr/local/mysql/bin/mysqld(+0xe44dcd)[0x55851fe72dcd]
      /lib64/libpthread.so.0(+0x7e75)[0x7f1881ef8e75]
      /lib64/libc.so.6(clone+0x6d)[0x7f1880d568fd]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): 
      Connection ID (thread ID): 28318
      Status: KILL_QUERY
      

      I can not find the exact match, so probably it's some new bug.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jplindst Jan Lindström
              Reporter:
              valerii Valerii Kravchuk
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: