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

MariaDB Server Crashes

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.3.8, 10.3.9
    • N/A
    • Server
    • OS: CentOS release 6.9

    Description

      Hello,
      Currently we are evaluating MariaDB 10.3 on our staging environment and noticed following issue which crashes the server.

      Query - k.id = primary key
      table1 has 2653883 rows
      table2 has 1350638 rows

       
      SELECT
          m.xxx_id,m.yyy_id,n.name,CONVERT(CONVERT(n.name USING binary) USING utf8) as name 
      FROM  
          table1 m  JOIN table2 n on m.yyy_id = n.id and m.zzz_id = 121 
      WHERE 
          n.name in ('str1' COLLATE utf8_unicode_ci,'str2' COLLATE utf8_unicode_ci,..... 'str1000'); 
      

      Error Log

       
      180823 19:01:19 [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.3.9-MariaDB-log
      key_buffer_size=67108864
      read_buffer_size=1048576
      max_used_connections=4
      max_threads=602
      thread_count=11
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1928308 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f2bc80009a8
      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 = 0x7f2cc37e8d68 thread_stack 0x49000
      /usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x7f2cc457fc0e]
      /usr/libexec/mysqld(handle_fatal_signal+0x5ad)[0x7f2cc3ffb00d]
      /lib64/libpthread.so.0(+0x34ac40f7e0)[0x7f2cc34067e0]
      /lib64/libc.so.6(+0x34ac13394f)[0x7f2cc1b6194f]
      /usr/libexec/mysqld(_ZN11String_list10append_strEP11st_mem_rootPKc+0x2d)[0x7f2cc3f0cefd]
      /usr/libexec/mysqld(_ZN17Explain_index_use3setEP11st_mem_rootP6st_keyj+0x88)[0x7f2cc3f0d198]
      /usr/libexec/mysqld(_ZN13st_join_table17save_explain_dataEP20Explain_table_accessybPS_+0x334)[0x7f2cc3e254a4]
      /usr/libexec/mysqld(_ZN4JOIN24save_explain_data_internEP13Explain_querybbbPKc+0xbe7)[0x7f2cc3e2bd97]
      /usr/libexec/mysqld(_ZN4JOIN17save_explain_dataEP13Explain_querybbbb+0xab)[0x7f2cc3e2bf2b]
      /usr/libexec/mysqld(_ZN4JOIN13build_explainEv+0x91)[0x7f2cc3e2c161]
      /usr/libexec/mysqld(_ZN4JOIN8optimizeEv+0x6b)[0x7f2cc3e45adb]
      /usr/libexec/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x93)[0x7f2cc3e48b13]
      /usr/libexec/mysqld(_Z19mysql_explain_unionP3THDP18st_select_lex_unitP13select_result+0x113)[0x7f2cc3e49613]
      /usr/libexec/mysqld(+0x5ad0b2)[0x7f2cc3de40b2]
      /usr/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x3a1f)[0x7f2cc3de9b9f]
      /usr/libexec/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x254)[0x7f2cc3defe44]
      /usr/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x236c)[0x7f2cc3df336c]
      /usr/libexec/mysqld(_Z10do_commandP3THD+0x18f)[0x7f2cc3df3e2f]
      /usr/libexec/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x22f)[0x7f2cc3edd3af]
      /usr/libexec/mysqld(handle_one_connection+0x44)[0x7f2cc3edd544]
      /lib64/libpthread.so.0(+0x34ac407aa1)[0x7f2cc33feaa1]
      /lib64/libc.so.6(clone+0x6d)[0x7f2cc1b16bcd]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
       
      Connection ID (thread ID): 10 
      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,split_materialized=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.
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            dgavhane Darshit Gavhane
            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.