Bug #92606 ysqld got signal 11
Submitted: 30 Sep 2018 7:44 Modified: 30 Sep 2018 9:00
Reporter: jessie jessie Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.7.21-21 OS:CentOS
Assigned to: CPU Architecture:Any

[30 Sep 2018 7:44] jessie jessie
Description:
we restore a slave,not have  another thread,just apply binlog. the server had crash many times.the memory is enough,i want know what's the wrong.is it MTS led to?
mysql version:5.7.21-21-log Percona Server (GPL), Release 21, Revision 2a37e4e
2018-09-29T22:37:24.026304+08:00 10 [Note] Multi-threaded slave statistics for channel '': seconds elapsed = 120; events assigned = 131106817; worker queues filled over overrun level = 0; waited due a Worker queue full = 0; waited due the total s
ize = 0; waited at clock conflicts = 5166304458600 waited (count) when Workers occupied = 287 waited when Workers occupied = 322627100
14:38:07 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://bugs.percona.com/

key_buffer_size=33554432
read_buffer_size=131072
max_used_connections=1
max_threads=10010
thread_count=10
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 83374237 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fd3c40008c0
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 = 7fd3f84a6d30 thread_stack 0x80000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xec6cdc]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x79bab1]
/lib64/libpthread.so.0(+0xf7e0)[0x7fee9e3d77e0]
/usr/sbin/mysqld(_Z27slave_worker_exec_job_groupP12Slave_workerP14Relay_log_info+0x21b)[0xe9cfab]
/usr/sbin/mysqld(handle_slave_worker+0x35b)[0xe801bb]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xedeb84]
/lib64/libpthread.so.0(+0x7aa1)[0x7fee9e3cfaa1]
/lib64/libc.so.6(clone+0x6d)[0x7fee9c6c6c4d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fd30af61350): is an invalid pointer
Connection ID (thread ID): 12
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.

How to repeat:
Unknown
[30 Sep 2018 9:00] Miguel Solorzano
Thank you for the bug report. Not repeatable test case was provided and the server isn't a MySQL Oracle binary please report the bug to Percona.