crash with assertion failure in lock0lock.cc

[Jo Holvoet]

This MAY be a duplicate of 1364840, but line number and stack trace show some differences :

2014-09-22 15:55:09 7f6ef08e0700 InnoDB: Assertion failure in thread 140114458969856 in file lock0lock.cc line 3980
InnoDB: Failing assertion: lock != ctx->wait_lock
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:55:09 UTC - mysqld got signal 6 ;
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=220
max_threads=1002
thread_count=197
connection_count=195
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 32985217 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x12d8f100
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 = 7f6ef08dfd38 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8f5835]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x664384]
/lib64/libpthread.so.0[0x302580f710]
/lib64/libc.so.6(gsignal+0x35)[0x3025432635]
/lib64/libc.so.6(abort+0x175)[0x3025433e15]
/usr/sbin/mysqld[0x9413ed]
/usr/sbin/mysqld[0x946947]
/usr/sbin/mysqld[0x947794]
/usr/sbin/mysqld[0x947b89]
/usr/sbin/mysqld[0x947ed3]
/usr/sbin/mysqld[0x9b9c9f]
/usr/sbin/mysqld[0x9bfe74]
/usr/sbin/mysqld[0x914d77]
/usr/sbin/mysqld(_ZN7handler11ha_rnd_nextEPh+0x65)[0x59f985]
/usr/sbin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x1e)[0x82b1be]
/usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x115c)[0x75e29c]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x12ff)[0x6e987f]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x658)[0x6eedc8]
/usr/sbin/mysqld[0x6eef21]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1362)[0x6f0a92]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x20a)[0x6f261a]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x6bb06f]
/usr/sbin/mysqld(handle_one_connection+0x47)[0x6bb247]
/usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0xaee54a]
/lib64/libpthread.so.0[0x30258079d1]
/lib64/libc.so.6(clone+0x6d)[0x30254e886d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f6bf460d7b0): is an invalid pointer
Connection ID (thread ID): 15006
Status: NOT_KILLED

[Jo Holvoet (jo-holvoet)]

Forgot the most important info of course :

Percona-XtraDB-Cluster-56.x86_64 1:5.6.20-25.7.888.el6 @percona
Percona-XtraDB-Cluster-client-56.x86_64 1:5.6.20-25.7.888.el6 @percona
Percona-XtraDB-Cluster-galera-3.x86_64 3.7-1.3254.rhel6 @percona
Percona-XtraDB-Cluster-server-56.x86_64 1:5.6.20-25.7.888.el6 @percona
Percona-XtraDB-Cluster-shared-56.x86_64 1:5.6.20-25.7.888.el6 @percona