Bug #88076 Server crash : InnoDB: Assertion failure in thread...in file rem0rec.cc line 580
Submitted: 12 Oct 2017 10:46 Modified: 12 Oct 2017 13:48
Reporter: Thomas VILLENA Email Updates:
Status: Unsupported Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:5.6.24-72.2 OS:CentOS (6.6 kernel : 2.6.32-504.23.4.el6.x86_64)
Assigned to: CPU Architecture:Any

[12 Oct 2017 10:46] Thomas VILLENA
we have a running cluster with 3 nodes. One of the servers crashes this night with following error messages:

2017-10-12 00:00:17 7f66d9aeb700  InnoDB: Assertion failure in thread 140079715497728 in file rem0rec.cc line 580
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.
22:00:17 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

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 25753926 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f672a84d000
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 = 7f66d9aeacf8 thread_stack 0x40000

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

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.
171012 00:00:23 mysqld_safe Number of processes running now: 0
171012 00:00:23 mysqld_safe WSREP: not restarting wsrep node automatically
171012 00:00:23 mysqld_safe mysqld from pid file /data/var/lib/mysql/ns-pandb01.nextsourcia.com.pid ended

Our Perona XtraDB Cluster:


We don't know why and how it's happended...



How to repeat:
 don't know how to reproduce it 

Suggested fix:
 don't know how to fix it
[12 Oct 2017 13:41] Shane Bester
If you can repeat this on Oracle MySQL server from dev.mysql.com feel free to open a report.  but this looks like Percona/Galera build to me, which Oracle cannot support.
[12 Oct 2017 13:43] Shane Bester
[12 Oct 2017 13:44] Shane Bester
[12 Oct 2017 13:48] Thomas VILLENA

OK we will see this with Percona.
Thanks you for these links and your help!