percona server 5.7 crashes with signal 11 3merge_buffersP10Sort_paramP11st_io_cache in backtrace
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
||||
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
New
|
Undecided
|
Unassigned | |||
5.6 |
New
|
Undecided
|
Unassigned | |||
5.7 |
Triaged
|
High
|
Unassigned |
Bug Description
Server version: 5.7.15-9-log Percona Server (GPL), Release '9', Revision '9f0fd0a'
uname -a
Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-
error log:
14:12:20 UTC - mysqld got signal 11 ;
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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_
read_buffer_
max_used_
max_threads=201
thread_count=2
connection_count=1
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: 0x7f7890000ae0
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 = 7f78bc313e80 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib/x86_
/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/
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f7890005790): DELETE p from parent p JOIN child c ON c.guid = p.guid WHERE c.int = 1167073
Connection ID (thread ID): 4
Status: NOT_KILLED
You may download the Percona Server operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
Writing a core file
Segmentation fault (core dumped)
How to reproduce:
As this situation disappears after running OPTIMIZE TABLE or reloading data from backup, I attach xtrabackup archive, on which this issue can be reproduced.
File is ~300mb size, so i was unable to attach it to bug.
https:/
mysql -uroot
mysql>use filemrirror;
mysql>START TRANSACTION;
mysql>DELETE p from parent p JOIN child c ON c.guid = p.guid WHERE c.int = 1167073;
mysql>ROLLBACK;
tags: | added: upstream |
Confirmed as described. Running tests on upstream MySQL 5.7.17.
12:43:50 UTC - mysqld got signal 11 ;
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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_ size=8388608 size=131072 connections= 1 size)*max_ threads = 68190 K bytes of memory
read_buffer_
max_used_
max_threads=151
thread_count=1
connection_count=1
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: 0x7fe878000ae0 mysqld( my_print_ stacktrace+ 0x3b)[0xe82a2b] mysqld( handle_ fatal_signal+ 0x489)[ 0x785a89] 64-linux- gnu/libpthread. so.0(+0x11390) [0x7fe8c1056390 ] 64-linux- gnu/libc. so.6(+0x9ede4) [0x7fe8c0479de4 ] mysqld( _Z13merge_ buffersP10Sort_ paramP11st_ io_cacheS2_ 20Bounds_ checked_ arrayIhEP11Merg e_chunkS3_ IS5_Ei+ 0x6a1)[ 0x7c5201] mysqld( _ZN6Unique3getE P5TABLE+ 0x2fd)[ 0xcf85ed] mysqld( _ZN19Query_ result_ delete10do_ deletesEv+ 0x82)[0xdbbbe2] mysqld( _ZN19Query_ result_ delete8send_ eofEv+0x42) [0xdbbc72] mysqld( _ZN4JOIN4execEv +0x6ad) [0xc1508d] mysqld( _Z12handle_ queryP3THDP3LEX P12Query_ resultyy+ 0x233)[ 0xc85a83] mysqld( _ZN20Sql_ cmd_delete_ multi7executeEP 3THD+0x27e) [0xdbb81e] mysqld( _Z21mysql_ execute_ commandP3THDb+ 0x24c5) [0xc465a5] mysqld( _Z11mysql_ parseP3THDP12Pa rser_state+ 0x3f5)[ 0xc4aea5] mysqld( _Z16dispatch_ commandP3THDPK8 COM_DATA19enum_ server_ command+ 0x1053) [0xc4bf63] mysqld( _Z10do_ commandP3THD+ 0x1c7)[ 0xc4d457] mysqld( handle_ connection+ 0x288)[ 0xd0ce38] mysqld( pfs_spawn_ thread+ 0x1b4)[ 0x11f1784] 64-linux- gnu/libpthread. so.0(+0x76ba) [0x7fe8c104c6ba ] 64-linux- gnu/libc. so.6(clone+ 0x6d)[0x7fe8c04 e182d]
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 = 7fe89c7f7e70 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
/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/
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fe8780054d0): is an invalid pointer
Connection ID (thread ID): 3
Status: NOT_KILLED
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.