MySQL crashes while donating SST

[Danny Gueta]

MySQL crashes on EC2 while donating SST, it seems to almost finish the process of donating but MySQL crashes before it ends.

SREP_SST: [INFO] Streaming with xbstream (20150116 00:41:19.855)
WSREP_SST: [INFO] Using socat as streamer (20150116 00:41:19.858)
WSREP_SST: [INFO] Using /tmp/tmp.N28006L6Lf as innobackupex temporary directory (20150116 00:41:20.070)
WSREP_SST: [INFO] Streaming GTID file before SST (20150116 00:41:20.080)
WSREP_SST: [INFO] Evaluating xbstream -c ${INFO_FILE} | socat -u stdio TCP:192.168.3.72:4444; RC=( ${PIPESTATUS[@]} ) (20150116 00:41:20.102)
WSREP_SST: [INFO] Sleeping before data transfer for SST (20150116 00:41:20.111)
2015-01-16 00:41:20 47165 [Note] WSREP: (2d805c4a, 'tcp://0.0.0.0:4567') turning message relay requesting off
WSREP_SST: [INFO] Streaming the backup to joiner at 192.168.3.72 4444 (20150116 00:41:30.119)
WSREP_SST: [INFO] Evaluating innobackupex --defaults-file=/etc/my.cnf --no-version-check $tmpopts $INNOEXTRA --galera-info --stream=$sfmt $itmpdir 2>${DATA}/innobackup.backup.log | socat -u stdio TCP:192.168.3.72:4444; RC=( ${PIPESTATUS[@]} ) (20150116 00:41:30.123)
06:49: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.
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 XtraDB Cluster better by reporting any
bugs at https://bugs.launchpad.net/percona-xtradb-cluster

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=172
max_threads=1002
thread_count=48
connection_count=37
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 408201 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xa6953640
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...
WSREP_SST: [ERROR] innobackupex finished with error: 9. Check /data/mysql/databases//innobackup.backup.log (20150116 01:49:20.550)
WSREP_SST: [ERROR] Cleanup after exit with status:22 (20150116 01:49:20.554)
WSREP_SST: [INFO] Cleaning up temporary directories (20150116 01:49:20.560)
2015-01-16 01:49:20 47165 [ERROR] WSREP: Failed to read from: wsrep_sst_xtrabackup-v2 --role 'donor' --address '192.168.3.72:4444/xtrabackup_sst//1' --auth 'sst:sstb4ckup!' --socket '/var/lib/mysql/mysql.sock' --datadir '/data/mysql/databases/' --defaults-file '/etc/my.cnf' --binlog '/data/mysql-bin/mysql-bin' --gtid '83e07a6f-96f8-11e3-b8f4-679cb41d96f9:15149696752'
2015-01-16 01:49:20 47165 [ERROR] WSREP: Process completed with error: wsrep_sst_xtrabackup-v2 --role 'donor' --address '192.168.3.72:4444/xtrabackup_sst//1' --auth 'sst:sstb4ckup!' --socket '/var/lib/mysql/mysql.sock' --datadir '/data/mysql/databases/' --defaults-file '/etc/my.cnf' --binlog '/data/mysql-bin/mysql-bin' --gtid '83e07a6f-96f8-11e3-b8f4-679cb41d96f9:15149696752': 22 (Invalid argument)
2015-01-16 01:49:20 47165 [ERROR] WSREP: Command did not run: wsrep_sst_xtrabackup-v2 --role 'donor' --address '192.168.3.72:4444/xtrabackup_sst//1' --auth 'sst:sstb4ckup!' --socket '/var/lib/mysql/mysql.sock' --datadir '/data/mysql/databases/' --defaults-file '/etc/my.cnf' --binlog '/data/mysql-bin/mysql-bin' --gtid '83e07a6f-96f8-11e3-b8f4-679cb41d96f9:15149696752'
2015-01-16 01:49:20 47165 [Warning] WSREP: 0.0 (dbm01): State transfer to 1.0 (dbm03) failed: -22 (Invalid argument)
2015-01-16 01:49:20 47165 [Note] WSREP: Shifting DONOR/DESYNCED -> JOINED (TO: 15152028524)
stack_bottom = 7ef0550ecdb8 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8f97d5]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x6655c4]
/lib64/libpthread.so.0(+0xf5b0)[0x7f12658255b0]
/usr/sbin/mysqld(_ZN8MDL_lock11Ticket_list13remove_ticketEP10MDL_ticket+0x15)[0x654d65]
/usr/sbin/mysqld(_ZN8MDL_lock13remove_ticketEMS_NS_11Ticket_listEP10MDL_ticket+0x93)[0x6578a3]
/usr/sbin/mysqld(_ZN11MDL_context12release_lockE17enum_mdl_durationP10MDL_ticket+0x1a)[0x65794a]
/usr/sbin/mysqld(_ZN18Global_backup_lock7releaseEP3THD+0x1f)[0x64af3f]
/usr/sbin/mysqld(_ZN3THD7cleanupEv+0x6d)[0x6b570d]
/usr/sbin/mysqld(_ZN3THD17release_resourcesEv+0x288)[0x6b6338]
/usr/sbin/mysqld(_Z29one_thread_per_connection_endP3THDb+0x2e)[0x5840ee]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x101)[0x6bc291]
/usr/sbin/mysqld(handle_one_connection+0x47)[0x6bc4f7]
/usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0xaf38ba]
/lib64/libpthread.so.0(+0x7f18)[0x7f126581df18]
/lib64/libc.so.6(clone+0x6d)[0x7f1263c92b2d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 472410
Status: KILL_CONNECTION

This has happened to me twice on 2 different machines, i've it tried it again and on the 3rd time it ran through fine with no changes to the machine or configuration.

[Danny Gueta (danny-gueta)]

forgot to mention we are running

PXC Server version: 5.6.21-70.1-56-log Percona XtraDB Cluster (GPL), Release rel70.1, Revision 938, WSREP version 25.8, wsrep_25.8.r4150

[Jervin R (revin)]

These 3 bugs appears to be closely related - we need backtrace from this crash to verify which one actually matches and get a better idea of what a fix would involve.

https://bugs.launchpad.net/percona-server/+bug/1405076
https://bugs.launchpad.net/percona-server/5.5/+bug/1403373
https://bugs.launchpad.net/percona-server/+bug/1371827

[Raghavendra D Prabhu (raghavendra-prabhu)]

Can you also provide /data/mysql/databases//innobackup.backup.log

[Raghavendra D Prabhu (raghavendra-prabhu)]

@Jervin,

Indeed, as you mentioned, this is an issue that needs to be fixed in PS.