Crash on RESET SLAVE ALL

Bug #1570695 reported by OrNix
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server moved to https://jira.percona.com/projects/PS
New
Undecided
Unassigned

Bug Description

Percona-server 5.7.11-4.1.el6, multi-source replication with bug (https://bugs.launchpad.net/percona-server/+bug/1562590). Server crashes on comman RESET SLAVE ALL

04:28:08 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=134217728
read_buffer_size=131072
max_used_connections=19
max_threads=501
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 330097 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fcfc80008c0
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 = 7fd06812cd40 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xec0a9c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x79b8c1]
/lib64/libpthread.so.0(+0xf500)[0x7fd2e4699500]
/usr/sbin/mysqld(_ZNSt8_Rb_treeISsSt4pairIKSsP11Master_infoESt10_Select1stIS4_ESt4lessISsESaIS4_EE4findERS1_+0x52)[0xe9b542]
/usr/sbin/mysqld(_ZN16Multisource_info9delete_miEPKc+0x1af)[0xe9a63f]
/usr/sbin/mysqld(_Z11reset_slaveP3THDP11Master_infob+0x1b2)[0xe833a2]
/usr/sbin/mysqld(_Z11reset_slaveP3THD+0x27a)[0xe8371a]
/usr/sbin/mysqld(_Z15reset_slave_cmdP3THD+0x120)[0xe83970]
/usr/sbin/mysqld(_Z20reload_acl_and_cacheP3THDmP10TABLE_LISTPi+0x3d5)[0xcd5f75]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x3fe8)[0xca4f28]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x5b5)[0xca85d5]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x92f)[0xca8f7f]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1b7)[0xcaa917]
/usr/sbin/mysqld(handle_connection+0x2a8)[0xd6b0a8]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0x12308d4]
/lib64/libpthread.so.0(+0x7851)[0x7fd2e4691851]
/lib64/libc.so.6(clone+0x6d)[0x7fd2e299190d]

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

Tags: upstream
Revision history for this message
Ramesh Sivaraman (rameshvs02) wrote :

Looks like upstream bug : http://bugs.mysql.com/bug.php?id=80302

tags: added: upstream
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3412

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.