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

SST failed and mariadbd stacktraced due to prepared transactions

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.4.18
    • Fix Version/s: 10.4
    • Component/s: Galera SST
    • Labels:
      None
    • Environment:
      Ubuntu 20.04

      Description

      We had the situation that we could not start nodes any more because the SST throws a stack trace after a prepared transactions.
      I have no clue how we came into this situation. But it was after restarting nodes and after upgrade from 10.4.17 to 10.4.18. But the system was previously not set-up 100% correct.

      2021-03-15 20:12:11 0 [Note] WSREP: Last wsrep seqno to be recovered 5636369
      2021-03-15 20:12:11 0 [ERROR] Found 1 prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or tc.log file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.
      2021-03-15 20:12:11 0 [ERROR] Aborting
      terminate called after throwing an instance of 'wsrep::runtime_error'
      what(): State wait was interrupted
      210315 20:12:11 [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.18-MariaDB-1:10.4.18+maria~focal-log
      key_buffer_size=134217728
      read_buffer_size=2097152
      max_used_connections=0
      max_threads=153
      thread_count=9
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1074864 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7fb6b0002118
      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 = 0x7fb6cbffdb78 thread_stack 0x49000
      /usr/sbin/mysqld(my_print_stacktrace+0x32)[0x5615fdbb7192]
      /usr/sbin/mysqld(handle_fatal_signal+0x55d)[0x5615fd66e54d]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x7fb6e129a3c0]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7fb6e098718b]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7fb6e0966859]
      /lib/x86_64-linux-gnu/libstdc++.so.6(+0x9e951)[0x7fb6e0d22951]
      /lib/x86_64-linux-gnu/libstdc++.so.6(+0xaa47c)[0x7fb6e0d2e47c]
      /lib/x86_64-linux-gnu/libstdc++.so.6(+0xaa4e7)[0x7fb6e0d2e4e7]
      /lib/x86_64-linux-gnu/libstdc++.so.6(+0xaa799)[0x7fb6e0d2e799]
      /usr/sbin/mysqld(+0x5d3434)[0x5615fd35e434]
      /usr/sbin/mysqld(_ZN5wsrep12server_state12sst_receivedERNS_14client_serviceEi+0xd93)[0x5615fdc2a3e3]
      /usr/sbin/mysqld(+0x85557f)[0x5615fd5e057f]
      /usr/sbin/mysqld(+0x856471)[0x5615fd5e1471]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609)[0x7fb6e128e609]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7fb6e0a63293]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): (null)
      Connection ID (thread ID): 3
      Status: NOT_KILLED

      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on

      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.

      We think the query pointer is invalid, but we will try to print it anyway.
      Query:

      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 0 unlimited bytes
      Max resident set unlimited unlimited bytes
      Max processes 87696 87696 processes
      Max open files 200000 200000 files
      Max locked memory 200000 200000 bytes
      Max address space unlimited unlimited bytes
      Max file locks unlimited unlimited locks
      Max pending signals 87696 87696 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/share/apport/apport %p %s %c %d %P %E

      Workaround: Stop node, remove contents of datadir, mysql_install_db, then sst worked.

        Attachments

          Activity

            People

            Assignee:
            jplindst Jan Lindström
            Reporter:
            oli Oli Sennhauser
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration