mysql56 crashes when executing insert

Bug #1599708 reported by XieAn
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
percona-projects-qa
New
Undecided
Unassigned

Bug Description

Server version: 5.6.29-76.2-log Source distribution

last night,suddenly crash,and in error File ,I found :

InnoDB: tried to purge sec index entry not marked for deletion in
InnoDB: index "idx_admin_id" of table "dw"."fct_service_record" /* Partition "p201606" */
InnoDB: tuple DATA TUPLE: 3 fields;
 0: len 4; hex 80000820; asc ;;
 1: len 4; hex 001fb83e; asc >;;
 2: len 3; hex 8fc0cb; asc ;;

InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 0
 0: len 4; hex 80000820; asc ;;
 1: len 4; hex 001fb83e; asc >;;
 2: len 3; hex 8fc0cb; asc ;;

2016-07-07 01:41:08 7fb259dc9700 InnoDB: Assertion failure in thread 140403988535040 in file row0ins.cc line 283
InnoDB: Failing assertion: *cursor->index->name == TEMP_INDEX_PREFIX
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.
17:41:08 UTC - mysqld got signal 6 ;
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.
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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=67108864
read_buffer_size=2097152
max_used_connections=823
max_threads=2002
thread_count=27
connection_count=27
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 8293382 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xa6803910
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 = 7fb259dc8e28 thread_stack 0x40000
/usr/local/webserver/percona/bin/mysqld(my_print_stacktrace+0x35)[0x9085f5]
/usr/local/webserver/percona/bin/mysqld(handle_fatal_signal+0x43b)[0x65ceeb]
/lib64/libpthread.so.0[0x3d8f80f7e0]
/lib64/libc.so.6(gsignal+0x35)[0x3d8f432625]
/lib64/libc.so.6(abort+0x175)[0x3d8f433e05]
/usr/local/webserver/percona/bin/mysqld[0x9f1e2d]
/usr/local/webserver/percona/bin/mysqld[0x9f45a0]
/usr/local/webserver/percona/bin/mysqld[0x9f5ccf]
/usr/local/webserver/percona/bin/mysqld[0xa02a4a]
/usr/local/webserver/percona/bin/mysqld[0x977c0f]
/usr/local/webserver/percona/bin/mysqld(_ZN7handler12ha_write_rowEPh+0x11f)[0x598eef]
/usr/local/webserver/percona/bin/mysqld(_ZN12ha_partition9write_rowEPh+0x11c)[0xb58c4c]
/usr/local/webserver/percona/bin/mysqld(_ZN7handler12ha_write_rowEPh+0xbd)[0x598e8d]
/usr/local/webserver/percona/bin/mysqld(_Z12write_recordP3THDP5TABLEP9COPY_INFOS4_+0x79)[0x6cbf19]
/usr/local/webserver/percona/bin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xabf)[0x6d357f]
/usr/local/webserver/percona/bin/mysqld(_Z21mysql_execute_commandP3THD+0x22c1)[0x6ebc41]
/usr/local/webserver/percona/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x598)[0x6ef198]
/usr/local/webserver/percona/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x16ca)[0x6f090a]
/usr/local/webserver/percona/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x115)[0x6b7795]
/usr/local/webserver/percona/bin/mysqld(handle_one_connection+0x42)[0x6b7912]
/usr/local/webserver/percona/bin/mysqld(pfs_spawn_thread+0x127)[0x944637]
/lib64/libpthread.so.0[0x3d8f807aa1]
/lib64/libc.so.6(clone+0x6d)[0x3d8f4e893d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7faba125fa40): is an invalid pointer
Connection ID (thread ID): 13620310
Status: NOT_KILLED

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.

InnoDB: Doing recovery: scanned up to log sequence number 37442258197504
InnoDB: Doing recovery: scanned up to log sequence number 37442260179030
InnoDB: Transaction 17095202233 was in the XA prepared state.
InnoDB: 4 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 15487866 row operations to undo
InnoDB: Trx id counter is 17095202560
2016-07-07 01:41:35 26126 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 2016-07-07 01:41:40 7fd6d290f700 InnoDB: unable to find a record to delete-mark
InnoDB: tuple DATA TUPLE: 3 fields;
 0: len 4; hex 80000820; asc ;;
 1: len 4; hex 001fb83e; asc >;;
 2: len 3; hex 8fc0cb; asc ;;

InnoDB: record PHYSICAL RECORD: n_fields 1; compact format; info bits 0
 0: len 8; hex 696e66696d756d00; asc infimum ;;

space 94332 offset 1002 (489 records, index id 115814)
InnoDB: Submit a detailed bug report to http://bugs.mysql.com

Revision history for this message
XieAn (xiepaup) wrote :

xiean@dw 11:27> show triggers; ---No Triggers and ,table structure is :
Empty set (0.00 sec)

xiean@dw 10:59> show create table fct_service_record\G
*************************** 1. row ***************************
       Table: fct_service_record
Create Table: CREATE TABLE `fct_service_record` (
  `record_id` int(11) unsigned NOT NULL COMMENT '记录单id',
  `source_no` varchar(50) DEFAULT '0' COMMENT '来源编号(live800,callcenter,意见反馈编号 唯一标识)',
  `admin_id` int(11) DEFAULT '0' COMMENT '记录单创建客服ID,dim_admin',
  `create_type` smallint(1) DEFAULT '1' COMMENT '记录单创建:1.自动创建 2.手动创建',
  `source_type` smallint(1) DEFAULT '0' COMMENT '来源类型(1.callcenter 2.live800 3.微信 4.旺旺 5.意见箱)',
  `belongs` smallint(1) DEFAULT '1' COMMENT '1.买家 2.卖家',
  `phone` char(20) DEFAULT '' COMMENT '来电电话',
  `user_id` int(11) DEFAULT '0' COMMENT '用户id',
  `user_name` varchar(64) DEFAULT NULL COMMENT '用户名称',
  `add_time` datetime DEFAULT NULL COMMENT '创建时间',
  `date_id` date NOT NULL DEFAULT '0000-00-00' COMMENT '创建日期',
  `is_event` smallint(1) NOT NULL DEFAULT '0' COMMENT '记录单是否有对应事件',
  `status` smallint(1) NOT NULL DEFAULT '1' COMMENT '记录单状态:0.删除 1.有效',
  `last_modified` datetime DEFAULT NULL COMMENT '最后修改时间,业务时间',
  `update_time` datetime DEFAULT NULL COMMENT 'etl加工时间',
  PRIMARY KEY (`record_id`,`date_id`),
  KEY `idx_admin_id` (`admin_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=4 COMMENT='客服记录单表'
/*!50500 PARTITION BY RANGE COLUMNS(date_id)
(PARTITION p201412 VALUES LESS THAN ('2015-01-01') ENGINE = InnoDB,
 PARTITION p201501 VALUES LESS THAN ('2015-02-01') ENGINE = InnoDB,
 PARTITION p201502 VALUES LESS THAN ('2015-03-01') ENGINE = InnoDB,
 PARTITION p201503 VALUES LESS THAN ('2015-04-01') ENGINE = InnoDB,
 PARTITION p201504 VALUES LESS THAN ('2015-05-01') ENGINE = InnoDB,
 PARTITION p201505 VALUES LESS THAN ('2015-06-01') ENGINE = InnoDB,
 PARTITION p201506 VALUES LESS THAN ('2015-07-01') ENGINE = InnoDB,
 PARTITION p201507 VALUES LESS THAN ('2015-08-01') ENGINE = InnoDB,
 PARTITION p201508 VALUES LESS THAN ('2015-09-01') ENGINE = InnoDB,
 PARTITION p201509 VALUES LESS THAN ('2015-10-01') ENGINE = InnoDB,
 PARTITION p201510 VALUES LESS THAN ('2015-11-01') ENGINE = InnoDB,
 PARTITION p201511 VALUES LESS THAN ('2015-12-01') ENGINE = InnoDB,
 PARTITION p201512 VALUES LESS THAN ('2016-01-01') ENGINE = InnoDB,
 PARTITION p201601 VALUES LESS THAN ('2016-02-01') ENGINE = InnoDB,
 PARTITION p201602 VALUES LESS THAN ('2016-03-01') ENGINE = InnoDB,
 PARTITION p201603 VALUES LESS THAN ('2016-04-01') ENGINE = InnoDB,
 PARTITION p201604 VALUES LESS THAN ('2016-05-01') ENGINE = InnoDB,
 PARTITION p201605 VALUES LESS THAN ('2016-06-01') ENGINE = InnoDB,
 PARTITION p201606 VALUES LESS THAN ('2016-07-01') ENGINE = InnoDB,
 PARTITION p201607 VALUES LESS THAN ('2016-08-01') ENGINE = InnoDB,
 PARTITION p201608 VALUES LESS THAN ('2016-09-01') ENGINE = InnoDB,
 PARTITION p201609 VALUES LESS THAN ('2016-10-01') ENGINE = InnoDB,
 PARTITION p201610 VALUES LESS THAN ('2016-11-01') ENGINE = InnoDB,
 PARTITION p201611 VALUES LESS THAN ('2016-12-01') ENGINE = InnoDB,
 PARTITION p201612 VALUES LESS THAN ('2017-01-01') ENGINE = InnoDB) */
1 row in set (0.00 sec)

XieAn (xiepaup)
Changed in percona-projects-qa:
status: New → Invalid
status: Invalid → New
MW (murrayw24)
no longer affects: centos
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.