InnoDB: Assertion failure in thread 140079715497728 in file line 580

Bug #1723079 reported by Thomas VILLENA on 2017-10-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to

Bug Description

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 line 580
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: 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

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 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/ ended

Our Perona XtraDB Cluster:


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


affects: percona-server → percona-xtradb-cluster
Krunal Bauskar (krunal-bauskar) wrote :

Check this thread

PXC inherited the upstream fix around 5.6.32. Please upgrade to latest version.

Changed in percona-xtradb-cluster:
status: New → Invalid

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers