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

mariadb crash while importing tablespace

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.3.39
    • N/A
    • None
    • None

    Description

      mariadb docker container crashed while importing tablespace

      2023-06-21  9:17:16 10 [Note] InnoDB: `filesender`.`Transfers` autoinc value set to 3051714
      2023-06-21 09:17:16 0x7fd23c5e2700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.3.39/storage/innobase/dict/dict0dict.cc line 1803
      InnoDB: Failing assertion: table->get_ref_count() == 0
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      230621  9:17:16 [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.3.39-MariaDB-1:10.3.39+maria~ubu2004 source revision: ca001cf2048f0152689e1895e2dc15486dd0b1af
      key_buffer_size=134217728
      read_buffer_size=2097152
      max_used_connections=2
      max_threads=102
      thread_count=6
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 760042 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7fd1fc007468
      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 = 0x7fd23c5e1dd8 thread_stack 0x49000
      mysqld(my_print_stacktrace+0x32)[0x560088279d42]
      mysqld(handle_fatal_signal+0x55d)[0x560087d4e19d]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x7fd24b63c420]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7fd24b47700b]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7fd24b456859]
      mysqld(+0x4ef47d)[0x560087a5547d]
      mysqld(+0x4fddf1)[0x560087a63df1]
      mysqld(+0x99f149)[0x560087f05149]
      mysqld(_Z34mysql_discard_or_import_tablespaceP3THDP10TABLE_LISTb+0xf6)[0x560087be8c86]
      mysqld(_ZN33Sql_cmd_discard_import_tablespace7executeEP3THD+0xac)[0x560087c47d1c]
      mysqld(_Z21mysql_execute_commandP3THD+0xdf8)[0x560087b4fec8]
      mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x1f3)[0x560087b57293]
      mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x105d)[0x560087b5966d]
      mysqld(_Z10do_commandP3THD+0x12d)[0x560087b5b61d]
      mysqld(_Z24do_handle_one_connectionP7CONNECT+0x246)[0x560087c45556]
      mysqld(handle_one_connection+0x3f)[0x560087c4572f]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x8609)[0x7fd24b630609]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7fd24b553133]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7fd1fc014f40): ALTER TABLE Transfers IMPORT TABLESPACE
       
      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 https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /var/lib/mysql
      Resource Limits:
      Limit                     Soft Limit           Hard Limit           Units
      Max cpu time              unlimited            unlimited            seconds
      Max file size             unlimited            unlimited            bytes
      Max data size             unlimited            unlimited            bytes
      Max stack size            8388608              unlimited            bytes
      Max core file size        unlimited            unlimited            bytes
      Max resident set          unlimited            unlimited            bytes
      Max processes             unlimited            unlimited            processes
      Max open files            1048576              1048576              files
      Max locked memory         65536                65536                bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       7229                 7229                 signals
      Max msgqueue size         819200               819200               bytes
      Max nice priority         0                    0
      Max realtime priority     0                    0
      Max realtime timeout      unlimited            unlimited            us
      Core pattern: |/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e %P %I %h
       
      Kernel version: Linux version 3.10.0-1160.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Mon Oct 19 16:18:59 UTC 2020
       
      Fatal signal 11 while backtracing
      
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              Mahmood Yaser
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.