Upgraded to version 5.6.35-26.20. Short while after a subsequent staggered reboot of nodes, they failed exhibiting hallmarks of bug 1232747.
Cluster total de-sync, attempted to bootstrap from single node but could only recover by downgrading to version 5.6.35-26.19.
See log output below for stack trace:
Version: '5.6.35-80.0-56-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Percona XtraDB Cluster (GPL), Release rel80.0, Revision 62752df, WSREP version 26.20, wsrep_26.20
2017-03-30 09:53:37 7815 [Note] WSREP: Initialized wsrep sidno 2
2017-03-30 09:53:37 7815 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2017-03-30 09:53:37 7815 [Note] WSREP: REPL Protocols: 7 (3, 2)
2017-03-30 09:53:37 7815 [Note] WSREP: Assign initial position for certification: 166051560, protocol version: 3
2017-03-30 09:53:37 7815 [Note] WSREP: Service thread queue flushed.
2017-03-30 09:53:37 7815 [Note] WSREP: GCache history reset: old(12d5ca61-b1a1-11e6-9911-7ec4afa00e5e:0) -> new(12d5ca61-b1a1-11e6-9911-7ec4afa00e5e:166051560)
2017-03-30 09:53:37 7815 [Note] WSREP: Synchronized with group, ready for connections
2017-03-30 09:53:37 7815 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check: __n (which is 4294967295) >= this->size() (which is 0)
08:53:59 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=16777216
read_buffer_size=131072
max_used_connections=10
max_threads=402
thread_count=20
connection_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 176557 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 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x9144ac]
/usr/sbin/mysqld(handle_fatal_signal+0x479)[0x68fc59]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f0221f37890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f021febd067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f021febe448]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x15d)[0x7f02207aab3d]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5ebb6)[0x7f02207a8bb6]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5ec01)[0x7f02207a8c01]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5ee19)[0x7f02207a8e19]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt24__throw_out_of_range_fmtPKcz+0x11f)[0x7f02207fecdf]
/usr/sbin/mysqld[0xaf01de]
/usr/sbin/mysqld[0xaf3599]
/usr/sbin/mysqld[0xaf62d5]
/usr/sbin/mysqld[0xaf7760]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f0221f30064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f021ff7062d]
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.
* Not sure if is regression or new issue.
* Can you help with test-case ?