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

test failures: rpl.rpl_stm_mixing_engines rpl.rpl_non_direct_mixed_mixing_engines rpl.rpl_mixed_mixing_engines rpl.rpl_row_mixing_engines rpl.rpl_non_direct_row_mixing_engines rpl.rpl_non_direct_stm_mixing_engines

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.2.8
    • N/A
    • Replication, Tests
    • None
    • Ubuntu-16.04 x86_64/ppc64le
       gcc --version
      gcc (Ubuntu 5.4.1-2ubuntu1~16.04) 5.4.1 20160904

    Description

      started occurring between e2afdb1ee430cb9d030aeeedc85eb903cda5e5d1 and 2a1035b004dfabcf3a7113be632b0030721a44d6 on x86_64 and ppc64le

      Attached test failures at 10.2(488f46f3de51070fa91e5eadcc215b6a4e343f7b)

      seems quite repeatable.

      Extract of backtrace:

      2017-08-03 16:38:45 140341213734656 [Note] Start binlog_dump to slave_server(2), pos(master-bin.000001, 4)
      170803 16:38:46 [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.2.8-MariaDB-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=7
      max_threads=153
      thread_count=14
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62983 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7fa35c0009a8
      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 = 0x7fa3bc2c7cf8 thread_stack 0x49000
      /home/danielgb/build-mariadb-server-10.2/sql/mysqld(my_print_stacktrace+0x29)[0x5562933884c9]
      /home/danielgb/build-mariadb-server-10.2/sql/mysqld(handle_fatal_signal+0x305)[0x556292e82e85]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fa3c4daf390]
      /home/danielgb/build-mariadb-server-10.2/sql/mysqld(_Z16first_linear_tabP4JOIN20enum_with_bush_roots22enum_with_const_tables+0x1d)[0x556292d31d7d]
      /home/danielgb/build-mariadb-server-10.2/sql/mysqld(_ZN13st_select_lex16set_explain_typeEb+0x18f)[0x556292cfa00f]
      /home/danielgb/build-mariadb-server-10.2/sql/mysqld(_ZN4JOIN24save_explain_data_internEP13Explain_querybbbPKc+0x131)[0x556292d4d321]
      /home/danielgb/build-mariadb-server-10.2/sql/mysqld(_ZN4JOIN8optimizeEv+0xa7)[0x556292d52cb7]
      mysys/stacktrace.c:268(my_print_stacktrace)[0x556292d8ef11]
      sql/sql_select.cc:8659(first_linear_tab(JOIN*, enum_with_bush_roots, enum_with_const_tables))[0x556292d8f175]
      sql/sql_lex.cc:4398(st_select_lex::set_explain_type(bool))[0x556292d92a6c]
      sql/sql_select.cc:351(handle_select(THD*, LEX*, select_result*, unsigned long))[0x556292d54cd4]
      sql/sql_parse.cc:4530(mysql_execute_command(THD*))[0x556292d0b30f]
      sql/sql_parse.cc:7879(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x556292d0bb7d]
      sql/sql_parse.cc:1817(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x556292d0e6a1]
      sql/sql_parse.cc:1364(do_command(THD*))[0x556292d0eed1]
      sql/sql_connect.cc:1354(do_handle_one_connection(CONNECT*))[0x556292dc9244]
      sql/sql_connect.cc:1262(handle_one_connection)[0x556292dc93b4]
      perfschema/pfs.cc:1865(pfs_spawn_thread)[0x5562932956c4]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fa3c4da56ba]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa3c42313dd]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7fa35c00efe0): INSERT INTO tt_1(trans_id, stmt_id, info) SELECT 32, 1, COUNT(*) FROM nt_1 UNION SELECT 24, 1, COUNT(*) FROM nt_1
      Connection ID (thread ID): 14
      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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
       
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      Writing a core file
      ----------SERVER LOG END-------------
       
       
       - saving '/home/danielgb/build-mariadb-server-10.2/mysql-test/var/3/log/rpl.rpl_non_direct_mixed_mixing_engines-innodb,mix/' to '/home/danielgb/build-mariadb-server-10.2/mysql-test/var/log/rpl.rpl_non_direct_mixed_mixing_engines-innodb,mix/'
      ***Warnings generated in error logs during shutdown after running tests: rpl.rpl_non_direct_mixed_mixing_engines
       
      170803 16:38:46 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out
      

      Attachments

        Issue Links

          Activity

            People

              psergei Sergei Petrunia
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.