cluster crashes on importing data
|Percona XtraDB Cluster||Status tracked in 5.6|
OS: Ubuntu 12.04 x64 - ALL updates made!
uname: Linux srzotrsDB01 3.5.0-45-generic #68~precise1-Ubuntu SMP Wed Dec 4 16:18:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
running under VMWare with 8GB RAM
top shows mysqld is using 4.5G RAM right before it crashes
mysql Ver 14.14 Distrib 5.6.15, for Linux (x86_64) using EditLine wrapper
Server-Type: Percona Server
Server Version: 5.6.15-62.0-log - Percona XtraDB Cluster (GPL), Release 62.0, wsrep_25.2.r4027
==> output of mysql client that is trying to load the data:
User time 493.34, System time 38.32
Maximum resident set size 33532, Integral resident set size 0
Non-physical pagefaults 9844, Physical pagefaults 178, Swaps 0
Blocks in 51202720 out 51202688, Messages in 0 out 0, Signals 0
Voluntary context switches 703541, Involuntary context switches 1211587
Thu Jan 9 14:44:00 CET 2014
2014-01-09 14:36:49 2070 [Note] WSREP: Created page /var/lib/
13:36:52 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:/
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7faa18000990
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
stack_bottom = 7faa503f2a50 thread_stack 0x80000
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 2
You may download the Percona XtraDB Cluster operations manual by visiting
in the manual which will help you identify the cause of the crash.
140109 14:36:57 mysqld_safe Number of processes running now: 0
140109 14:36:57 mysqld_safe WSREP: not restarting wsrep node automatically
140109 14:36:57 mysqld_safe mysqld from pid file /var/run/
|Changed in percona-xtradb-cluster:|
|status:||New → Incomplete|
|status:||Incomplete → New|
|Changed in galera:|
|assignee:||nobody → Alex Yurchenko (ayurchen)|
|milestone:||none → 25.3.5|
|status:||New → Fix Committed|
|Changed in galera:|
|status:||Fix Committed → Fix Released|