LP #1704719: percona cluster node crashes from time to time

**Reported in Launchpad by Darya Bessolitsyna last update 25-07-2017 17:21:37

Percona cluster nodes crashes from time to time.

Here is what we have installed:
Percona-XtraDB-Cluster-shared-56-5.6.35-26.20.3.el6.x86_64
Percona-XtraDB-Cluster-56-5.6.35-26.20.3.el6.x86_64
Percona-XtraDB-Cluster-56-debuginfo-5.6.35-26.20.3.el6.x86_64
Percona-XtraDB-Cluster-galera-3-3.20-3.el6.x86_64
percona-toolkit-2.1.7-1.noarch
Percona-XtraDB-Cluster-server-56-5.6.35-26.20.3.el6.x86_64
Percona-XtraDB-Cluster-client-56-5.6.35-26.20.3.el6.x86_64
percona-xtrabackup-2.3.8-1.el6.x86_64

Here is mysqld log:
2017-07-14 04:44:20 7f64ca1fc700 InnoDB: FTS Optimize Removing table media15540/contents2
2017-07-14 04:44:20 7f64ca1fc700 InnoDB: FTS Optimize Removing table media15540/persons
2017-07-14 04:44:20 7f64ca1fc700 InnoDB: FTS Optimize Removing table media15540/catalogItems
2017-07-14 04:44:21 7f64ca1fc700 InnoDB: FTS Optimize Removing table media15540/catalogItemTitles
15:04:49 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=33554432
read_buffer_size=2097152
max_used_connections=3
max_threads=502
thread_count=51
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2096212 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+0x35)[0x90f155]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x66d5f4]
/lib64/libpthread.so.0(+0xf7e0)[0x7f69e80397e0]
/usr/lib64/libgalera_smm.so(_ZN4asio6detail28reactive_socket_send_op_baseIN5boost5arrayINS_12const_bufferELm2EEEE10do_performEPNS0_10reactor_opE+0xcc)[0x7f69dfd0587c]
/usr/lib64/libgalera_smm.so(_ZN4asio6detail13epoll_reactor8start_opEiiRPNS1_16descriptor_stateEPNS0_10reactor_opEbb+0x14c)[0x7f69dfd1040c]
/usr/lib64/libgalera_smm.so(_ZN4asio6detail8write_opINS_19basic_stream_socketINS_2ip3tcpENS_21stream_socket_serviceIS4_EEEEN5boost5arrayINS_12const_bufferELm2EEENS0_14transfer_all_tENS8_3_bi6bind_tIvNS8_4_mfi3mf2IvN5gcomm13AsioTcpSocketERKNS_10error_codeEmEENSD_5list3INSD_5valueINS8_10shared_ptrISI_EEEEPFNS8_3argILi1EEEvEPFNSS_ILi2EEEvEEEEEEclESL_mi+0x356)[0x7f69dfd12456]
/usr/lib64/libgalera_smm.so(_ZN5gcomm13AsioTcpSocket9write_oneERKN5boost5arrayIN4asio12const_bufferELm2EEE+0x2e2)[0x7f69dfcfc972]
/usr/lib64/libgalera_smm.so(_ZN4asio6detail18completion_handlerIN5gcomm22AsioPostForSendHandlerEE11do_completeEPNS0_15task_io_serviceEPNS0_25task_io_service_operationERKNS_10error_codeEm+0x195)[0x7f69dfd173a5]
/usr/lib64/libgalera_smm.so(_ZN4asio10io_service3runEv+0x769)[0x7f69dfd266c9]
/usr/lib64/libgalera_smm.so(_ZN5gcomm12AsioProtonet10event_loopERKN2gu8datetime6PeriodE+0x259)[0x7f69dfd24a19]
/usr/lib64/libgalera_smm.so(_ZN9GCommConn3runEv+0xd3)[0x7f69dfd3d553]
/usr/lib64/libgalera_smm.so(_ZN9GCommConn6run_fnEPv+0x9)[0x7f69dfd40199]
/lib64/libpthread.so.0(+0x7aa1)[0x7f69e8031aa1]
/lib64/libc.so.6(clone+0x6d)[0x7f69e6328bcd]
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.
Writing a core file

General log, core dumps, libs are attached. Please let me know if anything else I could provide for more clarity on the issue.