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

Crash in wsrep_thd_LOCK() during IST

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Incomplete
    • Affects Version/s: 10.3.34
    • Fix Version/s: N/A
    • Component/s: Galera
    • Labels:
      None

      Description

      IST attempts end up with repeated crashes while applying write sets for different statements, with the following stack traces:

      ...
      2022-03-31 19:28:11 1 [Note] WSREP: Receiving IST: 649 writesets, seqnos 84978520-84979169
      2022-03-31 19:28:11 0 [Note] WSREP: Receiving IST... 0.0% ( 0/649 events) complete.
      2022-03-31 19:28:11 0 [Note] Reading of all Master_info entries succeeded
      2022-03-31 19:28:11 0 [Note] Added new Master_info '' to hash table
      2022-03-31 19:28:11 0 [Note] /opt/mysql/gc_mpi_prod_3306/bin/mysqld: ready for connections.
      Version: '10.3.34-MariaDB-log' socket: '/opt/mysql/mysql-gc_mpi_prod_3306.socket' port: 3306 MariaDB Server
      220331 19:28:12 [ERROR] mysqld got signal 11 ;
      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.3.34-MariaDB-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=1
      max_threads=102
      thread_count=16
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 355302 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f5324000c08
      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 = 0x7f5680058eb0 thread_stack 0x49000
      mysys/stacktrace.c:175(my_print_stacktrace)[0x5611eb58be5e]
      sql/signal_handler.cc:221(handle_fatal_signal)[0x5611eafdf6df]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f5721047730]
      psi/mysql_thread.h:692(inline_mysql_mutex_lock)[0x5611eaf4b053]
      sql/wsrep_mysqld.cc:2694(wsrep_thd_LOCK)[0x5611eaf4e3c4]
      handler/ha_innodb.cc:19090(wsrep_innobase_kill_one_trx(THD*, trx_t const*, trx_t*, char))[0x5611eb1bb1bc]
      lock/lock0lock.cc:1179(lock_rec_other_has_conflicting(unsigned long, buf_block_t const*, unsigned long, trx_t const*))[0x5611eb1fad6c]
      lock/lock0lock.cc:1952(lock_rec_lock(bool, unsigned long, buf_block_t const*, unsigned long, dict_index_t*, que_thr_t*))[0x5611eb201650]
      row/row0sel.cc:1320(sel_set_rec_lock(btr_pcur_t*, unsigned char const*, dict_index_t*, unsigned short const*, unsigned long, unsigned long, que_thr_t*, mtr_t*))[0x5611ead0f211]
      row/row0sel.cc:5156(row_search_mvcc(unsigned char*, page_cur_mode_t, row_prebuilt_t*, unsigned long, unsigned long))[0x5611eb29f50a]
      handler/ha_innodb.cc:9402(ha_innobase::index_read(unsigned char*, unsigned char const*, unsigned int, ha_rkey_function))[0x5611eb1c6b08]
      sql/handler.cc:2879(handler::ha_rnd_pos(unsigned char*, unsigned char*))[0x5611eafe4eea]
      sql/handler.h:3641(handler::rnd_pos_by_record(unsigned char*))[0x5611eafeddc3]
      sql/sql_class.h:6472(Rows_log_event::find_row(rpl_group_info*))[0x5611eb0e7c19]
      sql/log_event.cc:14650(Update_rows_log_event::do_exec_row(rpl_group_info*))[0x5611eb0e8360]
      sql/log_event.cc:11627(Rows_log_event::do_apply_event(rpl_group_info*))[0x5611eb0daf34]
      sql/log_event.h:1493(wsrep_apply_cb)[0x5611eaf59eec]
      src/trx_handle.cpp:316(galera::TrxHandle::apply(void*, wsrep_cb_status (*)(void*, void const*, unsigned long, unsigned int, wsrep_trx_meta const*), wsrep_trx_meta const&) const)[0x7f571be1923e]
      src/replicator_smm.cpp:92(apply_trx_ws(void*, wsrep_cb_status (*)(void*, void const*, unsigned long, unsigned int, wsrep_trx_meta const*), wsrep_cb_status (*)(void*, unsigned int, wsrep_trx_meta const*, bool*, bool), galera::TrxHandle const&, wsrep_trx_meta const&))[0x7f571be2af13]
      src/replicator_smm.cpp:458(galera::ReplicatorSMM::apply_trx(void*, galera::TrxHandle*))[0x7f571be2b0a8]
      src/gu_mutex.hpp:38(galera::ReplicatorSMM::recv_IST(void*))[0x7f571be39e7d]
      src/replicator_smm.cpp:368(galera::ReplicatorSMM::async_recv(void*))[0x7f571be2633b]
      src/wsrep_provider.cpp:271(galera_recv)[0x7f571be05b4b]
      sql/wsrep_thd.cc:488(wsrep_replication_process(THD*))[0x5611eaf5adb6]
      sql/wsrep_mysqld.cc:2179(start_wsrep_THD)[0x5611eaf4db7a]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7f572103cfa3]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f5720c644cf]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f56780160e3): UPDATE ... some different statement every time ...
      Connection ID (thread ID): 12
      Status: NOT_KILLED
      ...
      

      wsrep_slave_threads = 8 and cert.optimistic_ps = yes (default)

        Attachments

          Activity

            People

            Assignee:
            valerii Valerii Kravchuk
            Reporter:
            valerii Valerii Kravchuk
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.