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

InnoDB: Failing assertion: !index->to_be_dropped in file handler0alter.cc line 3490

    XMLWordPrintable

Details

    Description

      Note: this ugly test is only to reproduce the failure, please don't put it into the test suite, create a sensible one instead when the nature of the problem is known.

      Run with --repeat=N

      --source include/have_innodb.inc
       
      SET GLOBAL lock_wait_timeout = 3;
       
      --connect (con11,127.0.0.1,root,,test)
      --connect (con13,127.0.0.1,root,,test)
      --connect (con14,127.0.0.1,root,,test)
       
      --connection con13
      	CREATE TABLE IF NOT EXISTS t1 (col1 INT, col2 INT, col3 INT, col4 TEXT, KEY ftidx(col4(40))) ENGINE = InnoDB;
      --error ER_CANT_DROP_FIELD_OR_KEY
      	ALTER TABLE t1 DROP KEY idx;
       
      --connection con14
      --send
      	ALTER TABLE t1 ADD KEY idx ( col4(10), col2 ) /* QUERY_NO 3188 CON_ID 14 */;
      --connection con13
      --error ER_PARSE_ERROR
      	CREATE OR REPLACE VIEW v1 AS SYNTAX ERROR;
          START TRANSACTION;
      --send
      	INSERT INTO t1 (col1,col2,col3,col4) VALUES ( 4, 3, 4, REPEAT(CAST(4 AS CHAR(1)),@fill_amount));
      --connection con11
      --connection con14
      --error ER_LOCK_WAIT_TIMEOUT
      --reap
      --send
      	ALTER TABLE t1 DROP KEY ftidx, ADD KEY idx ( col4(10), col2 ) /* QUERY_NO 4164 CON_ID 14 */;
      --connection con11
      --send
      	ALTER TABLE t1 ADD UNIQUE KEY uidx ( col4(10), col2 ) /* QUERY_NO 4644 CON_ID 11 */;
       
      --connection con13
      --error 0,ER_LOCK_WAIT_TIMEOUT
      --reap
      --disconnect con13
       
      --connection con14
      --error 0,ER_LOCK_WAIT_TIMEOUT,ER_INDEX_CORRUPT
      --reap
      --disconnect con14
       
      --connection con11
      --error 0,ER_LOCK_WAIT_TIMEOUT
      --reap
      --disconnect con11
       
      --connection default
       
      DROP TABLE t1;
      SET GLOBAL lock_wait_timeout = DEFAULT;
      

      Stack trace from 10.0 commit b5fb2a685b6ec67d37033b020a8145d1aac1fc93

      2016-08-04 02:14:39 7f1f112a3700  InnoDB: Assertion failure in thread 139771408692992 in file handler0alter.cc line 3490
      InnoDB: Failing assertion: !index->to_be_dropped
      

      #5  0x00007f1f0f038448 in __GI_abort () at abort.c:89
      #6  0x00007f1f07b668b9 in ha_innodb::prepare_inplace_alter_table (this=0x7f1efc88b088, altered_table=0x7f1efc45f070, ha_alter_info=0x7f1f112a0270) at /data/src/10.0/storage/innobase/handler/handler0alter.cc:3490
      #7  0x000000000083a3f1 in handler::ha_prepare_inplace_alter_table (this=0x7f1efc88b088, altered_table=0x7f1efc45f070, ha_alter_info=0x7f1f112a0270) at /data/src/10.0/sql/handler.cc:4169
      #8  0x00000000006fa8ed in mysql_inplace_alter_table (thd=0x7f1f03768070, table_list=0x7f1efc4241e0, table=0x7f1efc955c70, altered_table=0x7f1efc45f070, ha_alter_info=0x7f1f112a0270, inplace_supported=HA_ALTER_INPLACE_NO_LOCK_AFTER_PREPARE, target_mdl_request=0x7f1f1129fcc0, alter_ctx=0x7f1f112a0850) at /data/src/10.0/sql/sql_table.cc:7062
      #9  0x00000000006fef73 in mysql_alter_table (thd=0x7f1f03768070, new_db=0x7f1efc4247c0 "test", new_name=0x0, create_info=0x7f1f112a14f0, table_list=0x7f1efc4241e0, alter_info=0x7f1f112a1460, order_num=0, order=0x0, ignore=false) at /data/src/10.0/sql/sql_table.cc:8885
      #10 0x0000000000766713 in Sql_cmd_alter_table::execute (this=0x7f1efc4248c8, thd=0x7f1f03768070) at /data/src/10.0/sql/sql_alter.cc:312
      #11 0x000000000064e9eb in mysql_execute_command (thd=0x7f1f03768070) at /data/src/10.0/sql/sql_parse.cc:5115
      #12 0x0000000000651e16 in mysql_parse (thd=0x7f1f03768070, rawbuf=0x7f1efc424088 "ALTER TABLE t1 ADD UNIQUE KEY uidx ( col4(10), col2 ) /* QUERY_NO 4644 CON_ID 11 */", length=83, parser_state=0x7f1f112a2650) at /data/src/10.0/sql/sql_parse.cc:6575
      #13 0x0000000000644922 in dispatch_command (command=COM_QUERY, thd=0x7f1f03768070, packet=0x7f1f0376e071 "ALTER TABLE t1 ADD UNIQUE KEY uidx ( col4(10), col2 ) /* QUERY_NO 4644 CON_ID 11 */", packet_length=83) at /data/src/10.0/sql/sql_parse.cc:1309
      #14 0x0000000000643be5 in do_command (thd=0x7f1f03768070) at /data/src/10.0/sql/sql_parse.cc:999
      #15 0x0000000000761e66 in do_handle_one_connection (thd_arg=0x7f1f03768070) at /data/src/10.0/sql/sql_connect.cc:1378
      #16 0x0000000000761bd8 in handle_one_connection (arg=0x7f1f03768070) at /data/src/10.0/sql/sql_connect.cc:1293
      #17 0x00000000009fa3a0 in pfs_spawn_thread (arg=0x7f1f03705e70) at /data/src/10.0/storage/perfschema/pfs.cc:1860
      #18 0x00007f1f10f320a4 in start_thread (arg=0x7f1f112a3700) at pthread_create.c:309
      #19 0x00007f1f0f0ea87d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
      

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f1efc424088): ALTER TABLE t1 ADD UNIQUE KEY uidx ( col4(10), col2 ) /* QUERY_NO 4644 CON_ID 11 */
      Connection ID (thread ID): 11
      Status: NOT_KILLED
      

      10.2 is also affected.

      Attachments

        Activity

          People

            jplindst Jan Lindström (Inactive)
            elenst Elena Stepanova
            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.