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

Mariadb crash on out of disk space during select into outfile

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Duplicate
    • Affects Version/s: 10.1.17
    • Fix Version/s: N/A
    • Component/s: OTHER
    • Labels:
    • Environment:
      CentOS x86_64 6.8, Amazon AWS m4.4xl instance

      Description

      I have MariaBD Galera cluster, but I suppose it's not a Galera issue, I had already 2 MariaDB server crashes, I suppose during "SELECT class.* FROM class INNER JOIN user ON class.teacher_id = user.id WHERE user.district_id = $DISTRICT_ID into outfile '/tmp/data/file.txt' fields terminated by ';' optionally enclosed by '\"' escaped by '' lines terminated by '\r\n'" -like queries when /tmp/ partition become out of disk space. Here are log files of these crashes:

      2016-09-03 20:35:43 139727889337088 [Note] InnoDB: Online DDL : Completed
      160904 3:02:46 [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.16-MariaDB
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=73
      max_threads=3002
      thread_count=38
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6724897 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0x7f14d484c008
      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 = 0x7f14341f8140 thread_stack 0x48400
      (my_addr_resolve failure: fork)
      /usr/sbin/mysqld(my_print_stacktrace+0x2b) [0x7f2067de3aab]
      /usr/sbin/mysqld(handle_fatal_signal+0x475) [0x7f2067940ef5]
      /lib64/libpthread.so.0(+0x3df100f7e0) [0x7f2066f467e0]
      /lib64/libc.so.6(memcpy+0x15b) [0x7f20653c495b]
      /usr/sbin/mysqld(_my_b_write+0x48) [0x7f2067dc91e8]
      /usr/sbin/mysqld(MYSQL_QUERY_LOG::write(THD*, long, char const*, unsigned int, unsigned long long, unsigned long long, bool, char const*, unsigned int)
      +0x534) [0x7f20679edf74]
      /usr/sbin/mysqld(Log_to_file_event_handler::log_slow(THD*, my_hrtime_t, char const*, unsigned int, unsigned long long, unsigned long long, bool, char c
      onst*, unsigned int)+0xde) [0x7f20679ee4ce]
      /usr/sbin/mysqld(LOGGER::slow_log_print(THD*, char const*, unsigned int, unsigned long long)+0x1f5) [0x7f20679e8585]
      /usr/sbin/mysqld(log_slow_statement(THD*)+0xf8) [0x7f20677c7558]
      /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x42d) [0x7f20677d6e3d]
      /usr/sbin/mysqld(do_command(THD*)+0x16b) [0x7f20677d923b]
      /usr/sbin/mysqld(do_handle_one_connection(THD*)+0x17f) [0x7f206789574f]
      /usr/sbin/mysqld(handle_one_connection+0x47) [0x7f20678958a7]
      /lib64/libpthread.so.0(+0x3df1007aa1) [0x7f2066f3eaa1]
      /lib64/libc.so.6(clone+0x6d) [0x7f2065423aad]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f150f595020): is an invalid pointer
      Connection ID (thread ID): 37181377
      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_co
      ndition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,se
      mijoin=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.

      We think the query pointer is invalid, but we will try to print it anyway.
      Query: SELECT cls.id FROM class cls INNER JOIN course crs ON cls.course_id = crs.id INNER JOIN school sch ON crs.school_id = sch.id WHERE s160904 03:02:47 mysqld_safe Number of processes running now: 0
      160904 03:02:47 mysqld_safe WSREP: not restarting wsrep node automatically
      160904 03:02:47 mysqld_safe mysqld from pid file /var/lib/mysql/db-east.edoctrina.org.pid ended

      Second:

      2016-09-17 20:56:11 140666973334272 [Note] InnoDB: Online DDL : End of building index `index_period_archived` (2 / 2)
      2016-09-17 20:56:11 140666973334272 [Note] InnoDB: Online DDL : Completed
      160918 3:02:40 [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.17-MariaDB
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=91
      max_threads=3002
      thread_count=37
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6725061 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0x7fed80149008
      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 = 0x7ff87f5fd140 thread_stack 0x48400
      (my_addr_resolve failure: fork)
      2016-09-18 03:02:40 7feb89c86b00/usr/sbin/mysqld(my_print_stacktrace+0x2b) [0x7ffb0d71916b]
      /usr/sbin/mysqld(handle_fatal_signal+0x475) [0x7ffb0d275375]
      /lib64/libpthread.so.0(+0x3df100f7e0) [0x7ffb0c87a7e0]
      /lib64/libc.so.6(memcpy+0x15b) [0x7ffb0acf895b]
      /usr/sbin/mysqld(_my_b_write+0x48) [0x7ffb0d6fe8a8]
      /usr/sbin/mysqld(MYSQL_QUERY_LOG::write(THD*, long, char const*, unsigned int, unsigned long long, unsigned long long, bool, char const*, unsigned int)
      +0x57c) [0x7ffb0d322aac]
      /usr/sbin/mysqld(Log_to_file_event_handler::log_slow(THD*, my_hrtime_t, char const*, unsigned int, unsigned long long, unsigned long long, bool, char c
      onst*, unsigned int)+0xde) [0x7ffb0d32301e]
      /usr/sbin/mysqld(LOGGER::slow_log_print(THD*, char const*, unsigned int, unsigned long long)+0x1f5) [0x7ffb0d31d075]
      /usr/sbin/mysqld(log_slow_statement(THD*)+0xf8) [0x7ffb0d0f94c8]
      /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x42d) [0x7ffb0d108dcd]
      /usr/sbin/mysqld(do_command(THD*)+0x16b) [0x7ffb0d10b1cb]
      /usr/sbin/mysqld(do_handle_one_connection(THD*)+0x17f) [0x7ffb0d1c9a5f]
      /usr/sbin/mysqld(handle_one_connection+0x47) [0x7ffb0d1c9bb7]
      /lib64/libpthread.so.0(+0x3df1007aa1) [0x7ffb0c872aa1]
      /lib64/libc.so.6(clone+0x6d) [0x7ffb0ad57aad]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7fefb7bf9020): is an invalid pointer
      Connection ID (thread ID): 23240690
      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_co
      ndition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,se
      mijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on InnoDB: Assertion failure in thread 140649605655296 in file buf0b
      uf.cc line 2657
      ,InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
      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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      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/do160918 03:02:41 mysqld_safe Number of processes running now: 0
      160918 03:02:41 mysqld_safe WSREP: not restarting wsrep node automatically
      160918 03:02:41 mysqld_safe mysqld from pid file /var/lib/mysql/db-east.edoctrina.org.pid ended
      160918 03:47:54 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
      160918 03:47:54 mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql/wsrep_recovery.Z5RKvX' --pid-file='/var/lib/mysql/db-east
      .edoctrina.org-recover.pid'
      2016-09-18 3:47:54 140408510490656 [Note] /usr/sbin/mysqld (mysqld 10.1.17-MariaDB) starting as process 103319 ...
      ...

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              kpvmaria Kaidalov Pavel
              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.