nodes out of sync - assertion failure in fil0fil.c

[Shane Peters]

Description

==================
After deploying three three nodes inside LXC containers on ppc64, two eventually
die off with the below after some time:

161203 1:23:32 [Note] WSREP: Quorum results:
        version = 2,
        component = PRIMARY,
        conf_id = 3,
        members = 2/2 (joined/total),
        act_id = 11574,
        last_appl. = 11546,
        protocols = 0/4/2 (gcs/repl/appl),
        group UUID = 662a7e74-b8ea-11e6-835c-93f3e79b4cfa
161203 1:23:32 [Note] WSREP: Flow-control interval: [23, 23]
161203 1:23:33 [Note] WSREP: New cluster view: global state: 662a7e74-b8ea-11e6-835c-93f3e79b4cfa:11574, view# 4: Primary, number of nodes: 2, my index: 0, protocol version 2
161203 1:23:33 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
161203 1:23:33 [Note] WSREP: Assign initial position for certification: 11574, protocol version: 2
161203 1:23:38 [Note] WSREP: cleaning up 8b3e9500-b8ea-11e6-b511-179fa3961d2c (tcp://10.0.0.193:4567)
161203 5:50:42 InnoDB: Assertion failure in thread 70365577277824 in file fil0fil.c line 5288
InnoDB: Failing assertion: node->n_pending > 0
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
05:50:42 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=33554432
read_buffer_size=131072
max_used_connections=423
max_threads=3002
thread_count=422
connection_count=422
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6603710 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+0x44)[0x52c5b114]
/usr/sbin/mysqld(handle_fatal_signal+0x500)[0x52aa6e20]
[0x3fffa9e60478]
/lib/powerpc64le-linux-gnu/libc.so.6(gsignal+0x48)[0x3fffa96b0ae8]
/lib/powerpc64le-linux-gnu/libc.so.6(abort+0x26c)[0x3fffa96b699c]
/usr/sbin/mysqld(+0x7643c0)[0x52d743c0]
/usr/sbin/mysqld(+0x771d34)[0x52d81d34]
/usr/sbin/mysqld(+0x6c2a08)[0x52cd2a08]
/lib/powerpc64le-linux-gnu/libpthread.so.0(+0x89a4)[0x3fffa9d489a4]
/lib/powerpc64le-linux-gnu/libc.so.6(clone+0x98)[0x3fffa978f400]
You may download the Percona XtraDB Cluster operations manual by visiting
http://www.percona.com/software/percona-xtradb-cluster/. You may find information
in the manual which will help you identify the cause of the crash.
161203 05:50:42 mysqld_safe Number of processes running now: 0
161203 05:50:42 mysqld_safe WSREP: not restarting wsrep node automatically
161203 05:50:42 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

Environment
===========
Trusty 14.04.5 LTS ppc64el

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mac Lin (mkl0301)]

FYI, this issue might be related to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1427406

We are able to get through this failure by back porting the mysql-5.6-trusty.patch to percona-xtradb-cluster-5.5. But there are other issues and not sure if related to this fix. But at least the mysqld is running.

[Mac Lin (mkl0301)]

BTW, we run the percona-cluster on ARM64 and see exactly the same error as this tickect does.