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

Assert during multi-master conflict abort

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0.7-galera
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Running conflicting multi-master load at MGC 10 cluster will soon result in assert like this:

      140319 17:58:40 [Note] WSREP: BF kill (1, seqno: 531598), victim: (6132) trx: 248136197
      140319 17:58:40 [Note] WSREP: Aborting query: COMMIT
      140319 17:58:40 [Note] WSREP: kill query for: 6132
      140319 17:58:40 [Note] WSREP: kill trx QUERY_COMMITTING for 248136197
      140319 17:58:40 [Note] WSREP: commit failed for reason: 3
      140319 17:58:40 [ERROR] WSREP: invalid state ROLLED_BACK (FATAL)
      at galera/src/replicator_smm.cpp:abort_trx():752
      140319 17:58:40 [ERROR] WSREP: cancel commit bad exit: 7 248136197
      140319 17:58:40 [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 http://kb.askmonty.org/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.0.7-MariaDB-wsrep
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=17
      max_threads=1026
      thread_count=14
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2368169 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0x7f2975c12008
      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 = 0x7f29f387f9c8 thread_stack 0x48000
      mysys/stacktrace.c:247(my_print_stacktrace)[0xac7bee]
      sql/signal_handler.cc:153(handle_fatal_signal)[0x6fdfa0]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0xfbb0)[0x7f29f2f9ebb0]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f29f1db7f77]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f29f1dbb5e8]
      handler/ha_innodb.cc:16814(wsrep_innobase_kill_one_trx(void*, trx_t const*, trx_t*, unsigned long))[0x88542d]
      lock/lock0lock.cc:1677(wsrep_kill_victim)[0x8a82b5]
      lock/lock0lock.cc:1711(lock_rec_other_has_conflicting)[0x8a86e5]
      lock/lock0lock.cc:1571(lock_rec_has_expl)[0x8b0151]
      lock/lock0lock.cc:6784(lock_clust_rec_read_check_and_lock(unsigned long, buf_block_t const*, unsigned char const*, dict_index_t*, unsigned long const*, lock_mode, unsigned long, que_thr_t*))[0x8b0bf0]

      How to reproduce:
      1. setup two node MGC 10 cluster
      2. run SQL load with writes on some hot-spot table, load balanced to both nodes.

        Attachments

          Activity

            People

            Assignee:
            seppo Seppo Jaakola
            Reporter:
            seppo Seppo Jaakola
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration