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

MariaDB Crash on Query Using Aria Engine

    XMLWordPrintable

Details

    • Bug
    • Status: Stalled (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.1.8, 5.5, 10.0, 10.1
    • 10.4
    • Storage Engine - Aria
    • Arch Linux 64bit

    Description

      Certain imports appear to be crashing MariaDB but only when this table is set to Aria as the engine, it doesn't happen when the table is set to InnoDB or MyISAM. Here's one example. Each time MariaDB was restarted, it kept crashing on this same insert.

      Thread pointer: 0x0x7fe6e0e54548
      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 = 0x7fea9ccb5d78 thread_stack 0x48000
      /usr/bin/mysqld(my_print_stacktrace+0x2e)[0x55b637b50a0e]
      /usr/bin/mysqld(handle_fatal_signal+0x34d)[0x55b63769fdcd]
      /usr/lib/libpthread.so.0(+0x10d60)[0x7fea9ad4fd60]
      /usr/bin/mysqld(+0x98299d)[0x55b637a9c99d]
      /usr/bin/mysqld(+0x982c3b)[0x55b637a9cc3b]
      /usr/bin/mysqld(+0x982a08)[0x55b637a9ca08]
      /usr/bin/mysqld(+0x982a08)[0x55b637a9ca08]
      /usr/bin/mysqld(+0x982e0b)[0x55b637a9ce0b]
      /usr/bin/mysqld(+0x983230)[0x55b637a9d230]
      /usr/bin/mysqld(+0x99cd43)[0x55b637ab6d43]
      /usr/bin/mysqld(+0x97fd10)[0x55b637a99d10]
      /usr/bin/mysqld(_ZN7handler12ha_write_rowEPh+0x42f)[0x55b6376a9cbf]
      /usr/bin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x6f)[0x55b6374fb2cf]
      /usr/bin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xf8e)[0x55b6374ff05e]
      /usr/bin/mysqld(_Z21mysql_execute_commandP3THD+0x325a)[0x55b637518eca]
      /usr/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x20e)[0x55b63751ecce]
      /usr/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x24a7)[0x55b637522087]
      /usr/bin/mysqld(_Z10do_commandP3THD+0x176)[0x55b6375227f6]
      /usr/bin/mysqld(_Z26threadpool_process_requestP3THD+0x127)[0x55b637629667]
      /usr/bin/mysqld(+0x55dc45)[0x55b637677c45]
      /usr/lib/libpthread.so.0(+0x74a4)[0x7fea9ad464a4]
      /usr/lib/libc.so.6(clone+0x6d)[0x7fea9a40413d]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7fe4d89648a0): INSERT INTO bookinfo          (title, author, asin, isbn, ean, url, salesrank, publisher, publishdate, pages,          overview, genre, cover, createddate, updateddate)         VALUES ('Standoff', 'Sandra Brown', '0743532627', '0743532627', '9780743532624', 'http://www.amazon.com/Standoff-Sandra-Brown/dp/0743532627%3FSubscriptionId%3DAKIAJ6YEOWNXMRGD5AFQ%26tag%3Dxnode0f-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D0743532627', 1230300, 'Simon & Schuster Audio', '2003-05-01', 6, ' TV reporter Tiel McCoy is driving down Interstate 20 on her way to New Mexico for a well-earned vacation. But her itinerary is rewritten when she hears on the radio that the teenage daughter of a well-known Fort Worth multi-millionaire has been kidnapped, at least that\'s the official report. In truth, she is pregnant and has run away with her boyfriend. After calling her editor, Tiel abandons her holiday plans in favor of pursuing the story.  During an innocuous visit to a convenience store in Rojo Flats, Tiel gets up close and personal with the barrel of a gun, two desperate young lovers -- and the scoop of a lifetime.  In the electrifying standoff that follows, she learns why the two young runaways fear the wealthy father of one of them even more than the FBI...and why she must defend them against a world bent on their destruction.  Poignant and riveting, Standoff is suspense at its best, as only Sandra Brown can create it.', 'Suspense', 1, now(), now())
      Connection ID (thread ID): 3259
      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.
      Mon Nov 16 13:18:23 2015 TokuFT recovery starting in env /var/lib/mysql/
      Mon Nov 16 13:18:23 2015 TokuFT recovery scanning backward from 5805517708
      Mon Nov 16 13:18:23 2015 TokuFT recovery bw_end_checkpoint at 5805517708 timestamp 1447679863009133 xid 5805505638 (bw_newer)
      Mon Nov 16 13:18:23 2015 TokuFT recovery bw_begin_checkpoint at 5805505638 timestamp 1447679844844486 (bw_between)
      Mon Nov 16 13:18:23 2015 TokuFT recovery turning around at begin checkpoint 5805505638 time 18164647
      Mon Nov 16 13:18:23 2015 TokuFT recovery starts scanning forward to 5805517708 from 5805505638 left 12070 (fw_between)
      Mon Nov 16 13:18:40 2015 TokuFT recovery scanning forward to 5805517708 at 5805507638 left 10070 (fw_between)
      Mon Nov 16 13:18:55 2015 TokuFT recovery scanning forward to 5805517708 at 5805515638 left 2070 (fw_between)
      Mon Nov 16 13:18:55 2015 TokuFT recovery closing 9765 dictionaries
      Mon Nov 16 13:19:01 2015 TokuFT recovery making a checkpoint
      Mon Nov 16 13:19:01 2015 TokuFT recovery done
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: The InnoDB memory heap is disabled
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: Memory barrier is not used
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: Compressed tables use zlib 1.2.8
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: Using Linux native AIO
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: Using CPU crc32 instructions
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: Initializing buffer pool, size = 128.0M
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: Completed initialization of buffer pool
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: Highest supported file format is Barracuda.
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: The log sequence numbers 706566915771 and 706566915771 in ibdata files do not match the log sequence number 706566915811 in the ib_logfiles!
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: Database was not shutdown normally!
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: Starting crash recovery.
      2015-11-16 13:19:01 139810053760896 [Note] InnoDB: Reading tablespace information from the .ibd files...
      2015-11-16 13:19:02 139810053760896 [Note] InnoDB: Restoring possible half-written data pages
      2015-11-16 13:19:02 139810053760896 [Note] InnoDB: from the doublewrite buffer...
      2015-11-16 13:19:02 139810053760896 [Note] InnoDB: 128 rollback segment(s) are active.
      2015-11-16 13:19:02 139810053760896 [Note] InnoDB: Waiting for purge to start
      2015-11-16 13:19:02 139810053760896 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 706566915811
      2015-11-16 13:19:03 139808592598784 [Note] InnoDB: Dumping buffer pool(s) not yet started
      2015-11-16 13:19:03 139810053760896 [Note] Plugin 'FEEDBACK' is disabled.
      2015-11-16 13:19:03 139810053760896 [Note] Recovering after a crash using tc.log
      2015-11-16 13:19:03 139810053760896 [Note] Starting crash recovery...
      2015-11-16 13:19:03 139810053760896 [Note] Crash recovery finished.
      2015-11-16 13:19:03 139810053760896 [Note] Event Scheduler: Loaded 0 events
      2015-11-16 13:19:03 139810053760896 [Note] /usr/bin/mysqld: ready for connections.
      Version: '10.1.8-MariaDB'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  MariaDB Server

      This is the table in question:

      CREATE TABLE `bookinfo` (
       `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
       `title` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
       `author` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
       `asin` varchar(128) COLLATE utf8_unicode_ci DEFAULT NULL,
       `isbn` varchar(128) COLLATE utf8_unicode_ci DEFAULT NULL,
       `ean` varchar(128) COLLATE utf8_unicode_ci DEFAULT NULL,
       `url` varchar(1000) COLLATE utf8_unicode_ci DEFAULT NULL,
       `salesrank` int(10) unsigned DEFAULT NULL,
       `publisher` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL,
       `publishdate` datetime DEFAULT NULL,
       `pages` varchar(128) COLLATE utf8_unicode_ci DEFAULT NULL,
       `overview` varchar(10000) COLLATE utf8_unicode_ci DEFAULT NULL,
       `genre` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
       `cover` tinyint(1) unsigned NOT NULL DEFAULT '0',
       `createddate` datetime NOT NULL,
       `updateddate` datetime NOT NULL,
       PRIMARY KEY (`id`) KEY_BLOCK_SIZE=2048,
       UNIQUE KEY `ix_bookinfo_asin` (`asin`) KEY_BLOCK_SIZE=2048,
       FULLTEXT KEY `ix_bookinfo_author_title_ft` (`author`,`title`) KEY_BLOCK_SIZE=2048
      ) ENGINE=Aria AUTO_INCREMENT=212983 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci PACK_KEYS=1 PAGE_CHECKSUM=0 ROW_FORMAT=DYNAMIC TRANSACTIONAL=0 /* `PAGE_COMPRESSED`=1 */

      (the table has been several different engines in the past which is why it appears to have retained many different and now invalid options).

      Attachments

        Issue Links

          Activity

            People

              monty Michael Widenius
              Enverex Benjamin Hodgetts
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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