Not the answer you need?
Register and ask your own question!

percona cluster crashed when loading data in batch

Dillon_luDillon_lu ContributorCurrent User Role Novice
Hi All,

My percona version is :Percona-XtraDB-Cluster-5.6.26-25.12-r624ef81-el5-x86_64-bundle

Below is the error messaga.
2015-12-08 05:24:43 4fb69940 InnoDB: Assertion failure in thread 1337366848 in file line 6011
InnoDB: Failing assertion: str_length <= tmp_length
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.
10:24:43 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 = 69123 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x18441e20
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 = 4fb69058 thread_stack 0x40000

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

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.
151208 05:24:43 mysqld_safe Number of processes running now: 0
151208 05:24:43 mysqld_safe WSREP: not restarting wsrep node automatically
151208 05:24:43 mysqld_safe mysqld from pid file /var/lib/mysql/ ended

What I do is to load data into a table with text fields:
`id` bigint(20) NOT NULL DEFAULT '0',
`jsid` bigint(20) NOT NULL DEFAULT '0',
`newstype` char(16) DEFAULT NULL,
`market` char(8) DEFAULT NULL,
`date` datetime DEFAULT NULL,
`title` varchar(511) DEFAULT NULL,
`media` varchar(127) DEFAULT NULL,
`author` varchar(127) DEFAULT NULL,
`content` mediumtext,
`relations` varchar(2048) DEFAULT NULL,
`stocks` varchar(1024) DEFAULT NULL,
`url` char(255) DEFAULT NULL,
`imgtype` int(11) DEFAULT NULL,
`imgext` char(8) DEFAULT NULL,
`imgsize` int(11) DEFAULT NULL,
`imgurl` char(255) DEFAULT NULL,
`deleted` int(1) DEFAULT '0',
UNIQUE KEY `ix_news_jsid` (`jsid`),
KEY `ix_news` (`newstype`,`market`,`date`),
FULLTEXT KEY `FID_relations` (`relations`)

This is a VM with 8G Mem. I used mysqldump and ETL to load data. By ETL, if I ignore content and relation columns, the transfer can be finished successfully; Otherwise, I'll get above errors. Is this a problem related to blob fields?

In mysql5.6 and percona5.6, I don't have this problem.
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.