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

Mariadb crashes with signal 11 when using federatedx engine and galera

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.1
    • Fix Version/s: 10.1.31
    • Labels:
      None
    • Environment:

      Description

      This is a clone of closed bug MDEV-14048
      We just encountered the crash on 10.1.28

      Tested on versions above.

      3 node galera installation, requests go to only one (primary node).

      Some queries against a database full of federatedx engine tables causes the server to crash. After restart the node syncs back to the cluster with no apparent damage.

      Not every query against the federatedx engine tables causes the crash. We were not able to identify the exact query. The ones suggested by log of query pointer after crash executed successfully when run by hand in console.

      Additional note:
      Disabling query cache seemed to have prevented the crash, but sent our server performance to the gutter. So we re-enabled the case and stopped using federatedx engine tables.

      Crash log:

      171103  8:13:21 [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.1.28-MariaDB
      key_buffer_size=67108864
      read_buffer_size=262144
      max_used_connections=91
      max_threads=3002
      thread_count=15
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1574808519 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f2d5bff4008
      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 = 0x7f3039cd7cb0 thread_stack 0xa0000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55d203c0092e]
      /usr/sbin/mysqld(handle_fatal_signal+0x305)[0x55d203723ce5]
      /lib64/libpthread.so.0(+0xf5e0)[0x7f31aac0b5e0]
      /usr/sbin/mysqld(_ZN17Query_cache_block11headers_lenEv+0x0)[0x55d20355d810]
      /usr/sbin/mysqld(_ZN17Query_cache_block4dataEv+0x11)[0x55d20355d831]
      /usr/sbin/mysqld(_ZN11Query_cache6insertEP3THDP15Query_cache_tlsPKcmj+0x5c)[0x55d20356121c]
      /usr/sbin/mysqld(net_real_write+0x45)[0x55d20350ae05]
      /usr/sbin/mysqld(net_flush+0x23)[0x55d20350b143]
      /usr/sbin/mysqld(net_write_command+0x3fb)[0x55d20350b8ab]
      /usr/sbin/mysqld(cli_advanced_command+0xe2)[0x55d203703782]
      /usr/sbin/mysqld(mysql_close_slow_part+0x54)[0x55d203700d44]
      /usr/sbin/mysqld(mysql_close+0x1a)[0x55d203700d7a]
      /usr/lib64/mysql/plugin/ha_federatedx.so(_ZN19federatedx_io_mysqlD1Ev+0x24)[0x7f309b1f9094]
      /usr/lib64/mysql/plugin/ha_federatedx.so(_ZN14federatedx_txn5closeEP18st_fedrated_server+0x69)[0x7f309b1f83b9]
      /usr/lib64/mysql/plugin/ha_federatedx.so(+0xa6ff)[0x7f309b1f16ff]
      /usr/lib64/mysql/plugin/ha_federatedx.so(+0xa8b5)[0x7f309b1f18b5]
      /usr/lib64/mysql/plugin/ha_federatedx.so(_ZN13ha_federatedx5closeEv+0x98)[0x7f309b1f5398]
      /usr/sbin/mysqld(_Z8closefrmP5TABLEb+0x38)[0x55d203643bf8]
      /usr/sbin/mysqld(_Z18intern_close_tableP5TABLE+0x36)[0x55d203550466]
      /usr/sbin/mysqld(_Z12tc_add_tableP3THDP5TABLE+0x42c)[0x55d2036d7dac]
      /usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0xccd)[0x55d20355300d]
      /usr/sbin/mysqld(_Z11open_tablesP3THDRK14DDL_options_stPP10TABLE_LISTPjjP19Prelocking_strategy+0x100a)[0x55d20355735a]
      /usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDRK14DDL_options_stP10TABLE_LISTbjP19Prelocking_strategy+0x34)[0x55d203557684]
      mysys/stacktrace.c:268(my_print_stacktrace)[0x55d2034d9fcc]
      sql/sql_cache.cc:844(Query_cache_block::headers_len())[0x55d20359e9b0]
      sql-common/client.c:3963(me/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.1.28/sql-common/client.c:3953)[0x55d2035a1702]
      sql/sql_string.h:312(String::free())[0x55d2035a2021]
      sql/table_cache.cc:291(tc_add_table(THD*, TABLE*))[0x55d2035a4971]
      sql/sql_parse.cc:5833(execute_sqlcom_select(THD*, TABLE_LIST*))[0x55d2035a59c6]
      sql/sql_connect.cc:1349(do_handle_one_connection(THD*))[0x55d20367161a]
      sql/sql_connect.cc:1263(handle_one_connection)[0x55d2036717c0]
      /lib64/libpthread.so.0(+0x7e25)[0x7f31aac03e25]
      /lib64/libc.so.6(clone+0x6d)[0x7f31a8fa734d]
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                serg Sergei Golubchik
                Reporter:
                jlunacek Jiri Lunacek
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: