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

the suddenly crashing in MariaDB10.1.29




      Install mariaDB10.1.29 in two database server (both centos7), one is master , another is slave.

      There are about 170 tables, 5 of them are spider engine (spider to the third database server),
      others are innoDB engine.

      Suddenly, some crashing occured , master was broken down . But auto repaired by mariadb soon, and now it's normally.

      Some info output in the error log :

      @180512 12:15:01 [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.29-MariaDB
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1023042 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0x7fa34576a008
      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 = 0x7fa3427fe190 thread_stack 0x48400
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): 
      Connection ID (thread ID): 21538
      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
      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.
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: The InnoDB memory heap is disabled
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: Compressed tables use zlib 1.2.7
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: Using Linux native AIO
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: Using generic crc32 instructions
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: Initializing buffer pool, size = 128.0M
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: Completed initialization of buffer pool
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: Highest supported file format is Barracuda.
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: The log sequence number 141678940 in ibdata file do not match the log sequence number 141687910 in the ib_logfiles!
      2018-05-12 12:15:07 140436573571328 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
      InnoDB: Last MySQL binlog file position 0 46478766, file name ./mysql-bin.000013
      2018-05-12 12:15:08 140436573571328 [Note] InnoDB: 128 rollback segment(s) are active.
      2018-05-12 12:15:08 140436573571328 [Note] InnoDB: Waiting for purge to start
      2018-05-12 12:15:08 140436573571328 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 141687910
      2018-05-12 12:15:08 140436573571328 [Note] Plugin 'FEEDBACK' is disabled.
      2018-05-12 12:15:08 140436573571328 [Note] Recovering after a crash using mysql-bin
      2018-05-12 12:15:08 140435527788288 [Note] InnoDB: Dumping buffer pool(s) not yet started
      2018-05-12 12:15:08 140436573571328 [Note] Starting crash recovery...
      2018-05-12 12:15:08 140436573571328 [Note] Crash recovery finished.
      2018-05-12 12:15:08 140436573571328 [Note] Server socket created on IP: '::'.
      2018-05-12 12:15:08 140436573571328 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--log-basename=#' or '--relay-log=ryukyu-malldb1-relay-bin' to avoid this problem.
      2018-05-12 12:15:08 140436573571328 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.1.29-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
      2018-05-12 12:45:02 140436572232448 [ERROR] mysqld: Table './mysql/spider_tables' is marked as crashed and should be repaired
      2018-05-12 12:45:02 140436572232448 [Warning] Checking table:   './mysql/spider_tables'

      About the reason of crashing , please help me find out.


        Issue Links



              jacob-mathew Jacob Mathew (Inactive)
              ting wangting
              0 Vote for this issue
              6 Start watching this issue



                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.