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

Spider Crash server in 10.3.7 Version

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 10.3.7
    • N/A
    • None
    • Windows

    Description

      Hi,

      we have upgraded to 10.3.7 because of some crashes in 10.1.25
      but still have crashes

      180621 13:02:30 [ERROR] mysqld got exception 0xc0000005 ;
      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.7-MariaDB-log
      key_buffer_size=536870912
      read_buffer_size=131072
      max_used_connections=3
      max_threads=65537
      thread_count=29
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 540890 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x5b244e6468
      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...
      mysqld.exe!??_9Item@@$BDFA@AA()
      mysqld.exe!?get_new_handler@@YAPEAVhandler@@PEAUTABLE_SHARE@@PEAUst_mem_root@@PEAUhandlerton@@@Z()
      mysqld.exe!?ha_delete_table@@YAHPEAVTHD@@PEAUhandlerton@@PEBDPEBUst_mysql_const_lex_string@@3_N@Z()
      mysqld.exe!?mysql_rm_table_no_locks@@YAHPEAVTHD@@PEAUTABLE_LIST@@_N22222@Z()
      mysqld.exe!?mysql_rm_table@@YA_NPEAVTHD@@PEAUTABLE_LIST@@_N22@Z()
      mysqld.exe!?mysql_execute_command@@YAHPEAVTHD@@@Z()
      mysqld.exe!?mysql_parse@@YAXPEAVTHD@@PEADIPEAVParser_state@@_N3@Z()
      mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PEAVTHD@@PEADI_N3@Z()
      mysqld.exe!?do_command@@YA_NPEAVTHD@@@Z()
      mysqld.exe!?pool_of_threads_scheduler@@YAXPEAUscheduler_functions@@PEAKPEAI@Z()
      mysqld.exe!?tp_callback@@YAXPEAUTP_connection@@@Z()
      ntdll.dll!RtlDosPathNameToNtPathName_U()
      ntdll.dll!RtlCompareUnicodeString()
      KERNEL32.DLL!BaseThreadInitThunk()
      ntdll.dll!RtlUserThreadStart()
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x5b2457bb80): DROP TABLE IF EXISTS DOCUMENT_ARCHIVE
      Connection ID (thread ID): 32
      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
      

      ---------------------------

      Server version: 10.3.7-MariaDB
      key_buffer_size=536870912
      read_buffer_size=131072
      max_used_connections=7
      max_threads=65537
      thread_count=32
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 540890 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0xe7a95e0e28
      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...
      ha_spider.dll!spider_ping_table_init()
      ha_spider.dll!spider_ping_table_init()
      mysqld.exe!?execute@Pushdown_query@@QEAAHPEAVJOIN@@@Z()
      mysqld.exe!?disjoin@?$List@VItem@@@@QEAAXPEAV1@@Z()
      mysqld.exe!?exec_inner@JOIN@@QEAAXXZ()
      mysqld.exe!?exec@JOIN@@QEAAXXZ()
      mysqld.exe!?mysql_select@@YA_NPEAVTHD@@PEAUTABLE_LIST@@IAEAV?$List@VItem@@@@PEAVItem@@IPEAUst_order@@434_KPEAVselect_result@@PEAVst_select_lex_unit@@PEAVst_select_lex@@@Z()
      mysqld.exe!?handle_select@@YA_NPEAVTHD@@PEAULEX@@PEAVselect_result@@K@Z()
      mysqld.exe!?execute_init_command@@YAXPEAVTHD@@PEAUst_mysql_lex_string@@PEAUst_mysql_rwlock@@@Z()
      mysqld.exe!?mysql_execute_command@@YAHPEAVTHD@@@Z()
      mysqld.exe!?mysql_parse@@YAXPEAVTHD@@PEADIPEAVParser_state@@_N3@Z()
      mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PEAVTHD@@PEADI_N3@Z()
      mysqld.exe!?do_command@@YA_NPEAVTHD@@@Z()
      mysqld.exe!?pool_of_threads_scheduler@@YAXPEAUscheduler_functions@@PEAKPEAI@Z()
      mysqld.exe!?tp_callback@@YAXPEAUTP_connection@@@Z()
      ntdll.dll!RtlDosPathNameToNtPathName_U()
      ntdll.dll!RtlCompareUnicodeString()
      KERNEL32.DLL!BaseThreadInitThunk()
      ntdll.dll!RtlUserThreadStart()
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0xe7ba755030): SELECT 1 FROM DOCUMENT_ARCHIVE LIMIT 1
      Connection ID (thread ID): 53
      Status: NOT_KILLED
       
      Optimizer switch: index_merge=on,index_merge_union=
      

      ------------------

      2018-06-21 12:46:19 28 [Warning] .\gedazur\doc_crit_archive.frm is inconsistent: engine typecode 44, engine name SPIDER (45)
      2018-06-21 12:46:21 28 [Warning] .\gedazur\doc_memo_archive.frm is inconsistent: engine typecode 44, engine name SPIDER (45)
      2018-06-21 12:46:32 28 [Warning] .\gedazur\document_archive.frm is inconsistent: engine typecode 44, engine name SPIDER (45)
      2018-06-21 12:57:44 64 [Warning] .\gedazur\doc_arbo_adr_archive.frm is inconsistent: engine typecode 44, engine name SPIDER (45)
      2018-06-21 12:57:44 64 [Warning] .\gedazur\document_archive.frm is inconsistent: engine typecode 44, engine name SPIDER (45)
      2018-06-21 12:57:44 64 [Warning] .\gedazur\doc_crit_archive.frm is inconsistent: engine typecode 44, engine name SPIDER (45)
      

      Attachments

        1. Aggregation_table_data.sql
          12 kB
        2. Aggregation-my.ini
          1 kB
        3. CPM-SERVER.err
          2.35 MB
        4. server_topology.xlsx
          12 kB
        5. Shard01_table_data.sql
          12 kB
        6. Shard01-my.ini
          0.9 kB
        7. Shard02_table_data.sql
          12 kB
        8. Shard02-my.ini
          0.7 kB
        9. Shard03_table_data.sql
          12 kB
        10. Shard03-my.ini
          0.7 kB

        Activity

          People

            jacob-mathew Jacob Mathew (Inactive)
            DjTOTOfr Antoine Girardi
            Votes:
            2 Vote for this issue
            Watchers:
            5 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.