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

Crash on derived query

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 10.0, 10.1
    • 10.0.23, 10.1.9
    • CentOS Linux 6.7, Nginx and PHP 5.6.12
      Linux 2.6.32-573.3.1.el6.x86_64 on x86_64
      Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz, 4 cores
    • 10.0.22, 10.1.9-1, 10.1.9-2

    Description

      MariaDB crashes with this query

      UPDATE 
      	data_entry 
      SET 
      	data_entry_cost = (
      		(
      			SELECT 
      				SUM(
      					data_exit_entry_quantity * data_entry_cost
      				)
      			FROM 
      				(
      					SELECT 
      						data_entry_exit_id, 
      						data_exit_entry_quantity, 
      						data_entry_cost 
      					FROM 
      						data_exit_entry 
      						INNER JOIN data_entry ON data_entry.data_entry_id = data_exit_entry.data_entry_id
      				) AS query 
      			WHERE 
      				data_entry_exit_id = data_entry.data_entry_id
      		)
      	) 

      Reference
      • Not crashing when InnoDB is used.
      • Only tested on Centos 6.7, maybe is specific to this plataform.
      • Crash seems not memory related.

      TABLES

       
      CREATE TABLE IF NOT EXISTS data_exit_entry (
        data_exit_entry_id int(11) NOT NULL,
        data_entry_id int(11) NOT NULL,
        data_entry_exit_id int(11) NOT NULL,
        data_exit_entry_quantity double NOT NULL
      ) ENGINE=MyISAM DEFAULT CHARSET=utf8;
       
      CREATE TABLE IF NOT EXISTS data_entry (
        data_entry_id int(11) NOT NULL,
        data_entry_cost double NOT NULL,
        data_entry_quantity double NOT NULL
      ) ENGINE=MyISAM DEFAULT CHARSET=utf8;
       

      Mysqld.log

       
      Version: '10.0.21-MariaDB-wsrep'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server, wsrep_25.10.r4144
      150829 14:31: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 http://kb.askmonty.org/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.0.21-MariaDB-wsrep
      key_buffer_size=402653184
      read_buffer_size=2097152
      max_used_connections=1
      max_threads=153
      thread_count=1
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1022970 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7f4b9ef66008
      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 = 0x7f4bc5c21d00 thread_stack 0x48000
      /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xba5fcb]
      /usr/sbin/mysqld(handle_fatal_signal+0x398)[0x749158]
      /lib64/libpthread.so.0(+0xf790)[0x7f4bc5853790]
      /usr/sbin/mysqld[0x604aae]
      /usr/sbin/mysqld[0x604f39]
      /usr/sbin/mysqld[0x60bb80]
      /usr/sbin/mysqld[0x60d75d]
      /usr/sbin/mysqld[0x52e9a9]
      /usr/sbin/mysqld(_ZN4JOIN14optimize_innerEv+0x6e1)[0x62d9d1]
      /usr/sbin/mysqld(_ZN4JOIN8optimizeEv+0x28)[0x62ff08]
      /usr/sbin/mysqld(_ZN13st_select_lex31optimize_unflattened_subqueriesEb+0x88)[0x5d4b28]
      /usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x3d5)[0x6748f5]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x3b8b)[0x5e12cb]
      /usr/sbin/mysqld[0x5e5a47]
      /usr/sbin/mysqld[0x5e640b]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x19fb)[0x5e834b]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x28a)[0x5e8cba]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x55b)[0x6a71bb]
      /usr/sbin/mysqld(handle_one_connection+0x42)[0x6a72b2]
      /lib64/libpthread.so.0(+0x7a51)[0x7f4bc584ba51]
      /lib64/libc.so.6(clone+0x6d)[0x7f4bc3f659ad]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f4b85421020): is an invalid pointer
      Connection ID (thread ID): 43
      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
       
      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.
      150829 14:31:19 mysqld_safe Number of processes running now: 0
      150829 14:31:19 mysqld_safe mysqld restarted
      150829 14:31:19 mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql/wsrep_recovery.xDqdu2' --pid-file='/var/lib/mysql/backup.xenoncloud.com-recover.pid'
      150829 14:31:19 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
      150829 14:31:19 [Note] /usr/sbin/mysqld (mysqld 10.0.21-MariaDB-wsrep) starting as process 8119 ...
      150829 14:31:22 mysqld_safe WSREP: Recovered position 00000000-0000-0000-0000-000000000000:-1
      150829 14:31:22 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
      150829 14:31:22 [Note] /usr/sbin/mysqld (mysqld 10.0.21-MariaDB-wsrep) starting as process 8152 ...
      150829 14:31:22 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      150829 14:31:22 [Note] InnoDB: The InnoDB memory heap is disabled
      150829 14:31:22 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      150829 14:31:22 [Note] InnoDB: Memory barrier is not used
      150829 14:31:22 [Note] InnoDB: Compressed tables use zlib 1.2.3
      150829 14:31:22 [Note] InnoDB: Using Linux native AIO
      150829 14:31:22 [Note] InnoDB: Not using CPU crc32 instructions
      150829 14:31:22 [Note] InnoDB: Initializing buffer pool, size = 128.0M
      150829 14:31:22 [Note] InnoDB: Completed initialization of buffer pool
      150829 14:31:22 [Note] InnoDB: Highest supported file format is Barracuda.
      150829 14:31:22 [Note] InnoDB: 128 rollback segment(s) are active.
      150829 14:31:22 [Note] InnoDB: Waiting for purge to start
      150829 14:31:22 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.25-73.1 started; log sequence number 1766038
      150829 14:31:22 [Note] Plugin 'FEEDBACK' is disabled.
      150829 14:31:22 [Note] Server socket created on IP: '::'.
      150829 14:31:22 [Note] Event Scheduler: Loaded 0 events
      150829 14:31:22 [Note] WSREP: Read nil XID from storage engines, skipping position init
      150829 14:31:22 [Note] WSREP: wsrep_load(): loading provider library 'none'
      150829 14:31:22 [Note] Reading of all Master_info entries succeded
      150829 14:31:22 [Note] Added new Master_info '' to hash table
      150829 14:31:22 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.0.21-MariaDB-wsrep'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server, wsrep_25.10.r4144

      Attachments

        Activity

          People

            sanja Oleksandr Byelkin
            master mexi
            Votes:
            0 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.