# percona5.6 bug?

**URL:** <https://forums.percona.com/t/percona5-6-bug/4574>\
**Category:** Other MySQL® Questions\
**Created:** [December 7, 2015, 5:52am UTC](https://forums.percona.com/t/percona5-6-bug/4574 "2015-12-07T05:52:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dillon\_lu](https://avatars.discourse-cdn.com/v4/letter/d/e19b73/32.png) [@Dillon\_lu](https://forums.percona.com/u/Dillon_lu)\
**Post date:** [December 7, 2015, 5:52am UTC](https://forums.percona.com/t/percona5-6-bug/4574/1 "2015-12-07T05:52:21Z")

</div>

I have this error when I import data into percona mysql.

2015-12-07 06:13:19 41697940 InnoDB: Assertion failure in thread 1097431360 in file ha\_innodb.cc line 6011  
InnoDB: Failing assertion: str\_length \<= tmp\_length  
InnoDB: We intentionally generate a memory trap.  
InnoDB: Submit a detailed bug report to [http://bugs.mysql.com](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: [url][http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html[/url]](http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html%5B/url%5D)  
InnoDB: about forcing recovery.  
11:13:19 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 [url][https://bugs.launchpad.net/percona-xtradb-cluster[/url]](https://bugs.launchpad.net/percona-xtradb-cluster%5B/url%5D)

This is my percona version:  
mysql\> select @@version,@@version\_comment;  
±---------------±--------------------------------------------------------------------------------------------+  
| @@version | @@version\_comment |  
±---------------±--------------------------------------------------------------------------------------------+  
| 5.6.26-74.0-56 | Percona XtraDB Cluster (GPL), Release rel74.0, Revision 1, WSREP version 25.12, wsrep\_25.12 |  
±---------------±--------------------------------------------------------------------------------------------+

I found a similar bug:  
[url][https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1347768[/url]](https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1347768%5B/url%5D)

In the bottom of this page, it was said this was fixed.

Is this a bug? Thanks.

---

<div class="post-metadata">

**Author:** ![Dillon\_lu](https://avatars.discourse-cdn.com/v4/letter/d/e19b73/32.png) [@Dillon\_lu](https://forums.percona.com/u/Dillon_lu)\
**Post date:** [December 8, 2015, 4:50am UTC](https://forums.percona.com/t/percona5-6-bug/4574/2 "2015-12-08T04:50:38Z")

</div>

I tired this against percona mysql server. It’s okay. The problem looks related to percona cluster server.