Killing a query inside InnoDB causes it to eventually crash with an assertion
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
|||
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Unassigned | ||
5.1 |
Fix Released
|
High
|
Unassigned | ||
5.5 |
Fix Released
|
High
|
Unassigned | ||
5.6 |
Fix Released
|
High
|
Unassigned |
Bug Description
RHEL 5.7, fully patched as of 2/27/2013.
Percona Server rhel5 rpm's for 5.1.67-rel14.3.506
Server is a slave, DB size = 2.8TB over 9600 tables 95% innodb, 5% myisam.
The following has happened twice today after upgrading from percona's 5.1.66-rel14.1.495 to 5.1.67-rel14.3.506 .
Stack trace and error message in in error log:
130227 13:16:27 InnoDB: Assertion failure in thread 1385572672 in file btr/btr0pcur.c line 245
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.
19:16:27 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://
key_buffer_
read_buffer_
max_used_
max_threads=3000
thread_count=150
connection_
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2abf00830eb0
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 = 529620f8 thread_stack 0x40000
/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/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
InnoDB Variables:
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_flush_method = ALL_O_DIRECT
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
expand_
innodb_
innodb_
innodb_
innodb_
transaction-
summary: |
- MySQL crash + Killing a query inside InnoDB causes it to eventually crash with an + assertion |
Thank you for the problem report. Please, attach part of the error log since last successful server startup and up to restart after this crash. I wonder if we will see the exact SELECT that crashed and some more details about the problem before the assertion.
Assertion happened in the btr_pcur_ restore_ position_ func():
if (UNIV_UNLIKELY( cursor- >old_stored != BTR_PCUR_ OLD_STORED) cursor- >pos_state != BTR_PCUR_ WAS_POSITIONED
&& cursor->pos_state != BTR_PCUR_ IS_POSITIONED) ) {
ut_print_ buf(stderr, cursor, sizeof( btr_pcur_ t));
putc( '\n', stderr); >trx_if_ known) {
trx_ print(stderr, cursor- >trx_if_ known, 0);
|| UNIV_UNLIKELY(
if (cursor-
}
}