XtraDB crash in insert / delete load
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona-XtraDB |
Won't Fix
|
High
|
Unassigned |
Bug Description
(gdb) bt
#0 0x00000033d7c30055 in raise () from /lib64/libc.so.6
#1 0x00000033d7c31af0 in abort () from /lib64/libc.so.6
#2 0x0000000000722179 in buf_page_get_zip (space=100062, zip_size=16384, offset=11919)
at ../../storage/
#3 0x000000000070c06c in btr_copy_
zip_size=16384, space_id=100062, page_no=0, offset=12) at btr/btr0cur.c:4441
#4 0x000000000070c703 in btr_rec_
zip_size=16384, no=<value optimized out>, len=0x45b1d230, heap=<value optimized out>) at btr/btr0cur.c:4692
#5 0x000000000079e0b1 in row_sel_
prebuilt=
#6 0x00000000007a02f5 in row_search_
prebuilt=
#7 0x00000000007028f2 in ha_innobase:
key_ptr=<value optimized out>, key_len=34, find_flag=
#8 0x0000000000664dff in handler:
end_key=<value optimized out>, eq_range_arg=<value optimized out>, sorted=<value optimized out>) at handler.cc:4155
#9 0x0000000000666c83 in handler:
range_count=1, sorted=<value optimized out>, buffer=<value optimized out>) at handler.cc:4029
#10 0x00000000006519fd in QUICK_RANGE_
#11 0x00000000006606ed in rr_quick (info=0x45b1ddd0) at records.cc:313
#12 0x000000000061b453 in mysql_delete (thd=0x4d37550, table_list=
limit=
#13 0x000000000059a6f7 in mysql_execute_
#14 0x000000000059d0fc in mysql_parse (thd=0x4d37550,
inBuf=0x4d41e30 "DELETE FROM sessions WHERE ID='c81e728d9d4
found_
#15 0x000000000059e0b8 in dispatch_command (command=COM_QUERY, thd=0x4d37550, packet=<value optimized out>,
packet_
#16 0x000000000059e616 in do_command (thd=0x4d37550) at sql_parse.cc:857
#17 0x0000000000591884 in handle_
#18 0x00000033d8c062f7 in start_thread () from /lib64/
#19 0x00000033d7cce85d in clone () from /lib64/libc.so.6
error.log
090213 19:40:34 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.31-
090213 19:43:12 InnoDB: Assertion failure in thread 1169295680 in file ../../storage/
InnoDB: Failing assertion: lock->reader_count > 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
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://
InnoDB: about forcing recovery.
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
Table definition:
CREATE TABLE `sessions` (
`ID` varchar(32) NOT NULL DEFAULT '',
`Last` int(11) NOT NULL DEFAULT '0',
`C` text NOT NULL,
PRIMARY KEY (`ID`),
KEY `Last` (`Last`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 KEY_BLOCK_SIZE=16
Changed in percona-xtradb: | |
assignee: | nobody → yasufumi-kinoshita |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in percona-xtradb: | |
status: | Confirmed → Fix Committed |
Changed in percona-xtradb: | |
status: | Fix Committed → In Progress |
Also there is reported problem with the similar insert / delete workload (replication thread)
090213 9:25:24 InnoDB: Assertion failure in thread 1316211008 in file btr/btr0cur.c line 4231 get_type( page) == FIL_PAGE_TYPE_BLOB bugs.mysql. com. dev.mysql. com/doc/ refman/ 5.1/en/ forcing- recovery. html mysqld( my_print_ stacktrace+ 0x2e)[0x819b2e] mysqld( handle_ segfault+ 0x322)[ 0x5817c2] libpthread. so.0[0x36e700de 70] libc.so. 6(gsignal+ 0x35)[0x36e6430 155] libc.so. 6(abort+ 0x110)[ 0x36e6431bf0] mysqld[ 0x6f3dfc] mysqld[ 0x77fea3] mysqld[ 0x76bf27] mysqld[ 0x799f87] mysqld[ 0x792df5] libpthread. so.0[0x36e70062 f7] libc.so. 6(clone+ 0x6d)[0x36e64d1 e3d]
InnoDB: Failing assertion: fil_page_
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
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://
InnoDB: about forcing recovery.
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
090213 9:25:24 - 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.
key_buffer_ size=402653184 size=1048576 connections= 0 size)*max_ threads = 37297841 K
read_buffer_
max_used_
max_threads=4000
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x0 dev.mysql. com/doc/ mysql/en/ crashing. html contains
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 = (nil) thread_stack 0x40000
The manual page at http://
information that should help you find out what is causing the crash.
and may be related to http:// forums. innodb. com/read. php?3,114, 114
I am not sure if it is the same bug or another