Percona Server moved to https://jira.percona.com/projects/PS

Comment 6 for bug 1732252

Revision history for this message

Francisco Bordenave (francisco-bordenave) wrote on 2018-01-09: Re: Percona Server crashes during stop/restart when using userstat=1 in multi-sourced slaves

Sveta, Laurynas,

I have some new info here, I could reproduce the crash in a single sourced slave (i.e. 1 master-1slave) and the stack trace looks a bit different crashing at the same point:

19:07:24 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=17179869184
read_buffer_size=131072
max_used_connections=5
max_threads=601
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17016081 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xed35ac]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7a15e1]
/lib64/libpthread.so.0[0x30f480f7e0]
/usr/sbin/mysqld(_ZN7handler25update_global_table_statsEv+0x17f)[0x80704f]
/usr/sbin/mysqld(_Z15close_temporaryP5TABLEbb+0xa6)[0xc53bc6]
/usr/sbin/mysqld(_ZN14Relay_log_info22close_temporary_tablesEv+0x3b)[0xe9e32b]
/usr/sbin/mysqld(_Z25delete_slave_info_objectsv+0x136)[0xe88a56]
/usr/sbin/mysqld(signal_hand+0x4a6)[0x793956]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0x1208a24]
/lib64/libpthread.so.0[0x30f4807aa1]
/lib64/libc.so.6(clone+0x6d)[0x30f44e8aad]
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.

Seems this portion is the key here:
/usr/sbin/mysqld(_ZN7handler25update_global_table_statsEv+0x17f)[0x80704f]

The failure happens during stop process and only happens with userstat=1.

Also it looks like there is some relation with userstat=1 and Slave_open_temp_tables>0 (not sure yet), tomorrow I should have root access here and probably trace the problem with gdb.

Sveta, Laurynas,

I have some new info here, I could reproduce the crash in a single sourced slave (i.e. 1 master-1slave) and the stack trace looks a bit different crashing at the same point:

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

Seems this portion is the key here: 
/usr/sbin/mysqld(_ZN7handler25update_global_table_statsEv+0x17f)[0x80704f]

The failure happens during stop process and only happens with userstat=1.

Also it looks like there is some relation with userstat=1 and Slave_open_temp_tables>0 (not sure yet), tomorrow I should have root access here and probably trace the problem with gdb.