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

CONNECT Engine crashes with JSON table type

Details

    Description

      A user using the CONNECT engine with JSON table types is seeing crashes like the following:

      mysqld: /home/buildbot/buildbot/build/mariadb-10.1.20/storage/connect/plugutil.c:520: PlugSubAlloc: Assertion `g->jump_level >= 0' failed.
      170418 19:59:53 [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.1.20-MariaDB
      key_buffer_size=1048576
      read_buffer_size=262144
      max_used_connections=24
      max_threads=502
      thread_count=22
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 653874 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7f66159d4008
      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 = 0x7f66ec523d40 thread_stack 0x3c000
      /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f66fcd085cb]
      /usr/sbin/mysqld(handle_fatal_signal+0x4d5)[0x7f66fc861375]
      /lib64/libpthread.so.0(+0xf7e0)[0x7f66fbe637e0]
      /lib64/libc.so.6(gsignal+0x35)[0x7f66fa2895e5]
      /lib64/libc.so.6(abort+0x175)[0x7f66fa28adc5]
      /lib64/libc.so.6(+0x2b70e)[0x7f66fa28270e]
      /lib64/libc.so.6(__assert_perror_fail+0x0)[0x7f66fa2827d0]
      /usr/lib64/mysql/plugin/ha_connect.so(PlugSubAlloc+0x16f)[0x7f66f630214f]
      /usr/lib64/mysql/plugin/ha_connect.so(_Z7SetPathP7_globalPKc+0x38)[0x7f66f6338138]
      mysys/stacktrace.c:268(my_print_stacktrace)[0x7f66f62f0107]
      /usr/lib64/mysql/plugin/ha_connect.so(_Z10CntCheckDBP7_globalP10ha_connectPKc+0x96)[0x7f66f62fce56]
      /usr/lib64/mysql/plugin/ha_connect.so(_ZN10ha_connect4openEPKcij+0xce)[0x7f66f62efcae]
      /usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcij+0x3e)[0x7f66fc86560e]
      sql/handler.cc:2501(handler::ha_open(TABLE*, char const*, int, unsigned int))[0x7f66fc7908f3]
      sql/table.cc:2930(open_table_from_share(THD*, TABLE_SHARE*, char const*, unsigned int, unsigned int, unsigned int, TABLE*, bool))[0x7f66fc6a95f5]
      sql/sql_base.cc:2554(open_table(THD*, TABLE_LIST*, Open_table_context*))[0x7f66fc6adb02]
      sql/sql_base.cc:5258(open_and_lock_tables(THD*, DDL_options_st const&, TABLE_LIST*, bool, unsigned int, Prelocking_strategy*))[0x7f66fc6ade84]
      /usr/sbin/mysqld(+0x451dd3)[0x7f66fc6e4dd3]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x5d8c)[0x7f66fc6f10fc]
      sql/sql_parse.cc:5817(execute_sqlcom_select)[0x7f66fc6f46b4]
      sql/sql_parse.cc:1487(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x7f66fc6f7183]
      sql/sql_parse.cc:1110(do_command(THD*))[0x7f66fc6f771b]
      sql/sql_connect.cc:1350(do_handle_one_connection(THD*))[0x7f66fc7b5fff]
      sql/sql_connect.cc:1264(handle_one_connection)[0x7f66fc7b6157]
      /lib64/libpthread.so.0(+0x7aa1)[0x7f66fbe5baa1]
      /lib64/libc.so.6(clone+0x6d)[0x7f66fa33faad]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f6614d5c020): is an invalid pointer
      Connection ID (thread ID): 22
      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=off
      

      Attachments

        Activity

          If really the crash occurs in this context (open->CntCheckDB->SetPath->PlugSubAlloc) it is strange that this only occurs here because these functions are called when opening all tables with no problem so far.

          Although I could not reproduce this, a crash can indeed happen here is case of memory exhausted. Therefore, I fixed this to return an error instead of crashing.

          However, not able to reproduce it, I cannot be sure this is really the cause of the crash.

          This why you should increase the CONNECT work memory by:

          set connect_work_size=<size>; // in number, no K, M or G

          The default size is 64M, which can be small for huge json files.
          If it works, this case will be able to be regarded as fixed.

          bertrandop Olivier Bertrand added a comment - If really the crash occurs in this context (open->CntCheckDB->SetPath->PlugSubAlloc) it is strange that this only occurs here because these functions are called when opening all tables with no problem so far. Although I could not reproduce this, a crash can indeed happen here is case of memory exhausted. Therefore, I fixed this to return an error instead of crashing. However, not able to reproduce it, I cannot be sure this is really the cause of the crash. This why you should increase the CONNECT work memory by: set connect_work_size=< size >; // in number, no K, M or G The default size is 64M, which can be small for huge json files. If it works, this case will be able to be regarded as fixed.

          See also (MDEV-12760]

          bertrandop Olivier Bertrand added a comment - See also ( MDEV-12760 ]

          People

            bertrandop Olivier Bertrand
            GeoffMontee Geoff Montee (Inactive)
            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.