Percona Cluster ERROR 2013 (HY000): Lost connection to MySQL server during query

MySQL & MariaDB Percona XtraDB Cluster 5.x
1

I have3 nodes in a cluster with 24GB of RAM, 8 cores and 300GB SSD on each node.

I have a partitioned database with 30 million entries. When I try to insert large amounts of data (about 10 million), from one table to another, I get the following error:

ERROR 2013 (HY000): Lost connection to MySQL server during query

The log mysql-error is the following:

150619 16:38:35 mysqld_safe Number of processes running now: 0
150619 16:38:35 mysqld_safe WSREP: not restarting wsrep node automatically
150619 16:38:35 mysqld_safe mysqld from pid file /var/lib/mysql/mysql.pid ended

The PXC versión is 5.6.24-72.2 and the config file:

# Generated by Percona Configuration Wizard (http://tools.percona.com/) version REL5-20120208
# Configuration name server-2026 generated for ximop_22@hotmail.com at 2015-01-14 08:51:46

[mysql]

# CLIENT #
port = 3306
socket = /var/lib/mysql/mysql.sock

[mysqld]

# GENERAL #
user = mysql
default-storage-engine = InnoDB
socket = /var/lib/mysql/mysql.sock
pid-file = /var/lib/mysql/mysql.pid
tmpdir = /dev/shm/mysqltmp/
server-id = 1
expire_logs_days = 7
delayed_insert_timeout = 3600
skip-host-cache
skip-name-resolve

# Cluster Config #
#wsrep_cluster_address=gcomm://
wsrep_cluster_address=gcomm://10.240.28.7,10.240.46.7,10.240.208.7
binlog_format=ROW
wsrep_provider=/usr/lib64/libgalera_smm.so
wsrep_cluster_name=AirePXC
wsrep_sst_method=xtrabackup-v2
wsrep_sst_auth="sstuser:s3cret"
wsrep_node_name=PXC1
wsrep_node_address=10.240.28.7
#innodb_locks_unsafe_for_binlog=1
transaction-isolation=READ-COMMITTED
innodb_autoinc_lock_mode=2

# MyISAM #
key-buffer-size = 32M
myisam-recover-options = FORCE,BACKUP

# SAFETY #
max-allowed-packet = 16M
max-connect-errors = 1000000

# DATA STORAGE #
datadir = /var/lib/mysql/

# BINARY LOGGING #
log-bin = /var/lib/mysql/mysql-bin
expire-logs-days = 2
sync-binlog = 0
log-slave-updates = 1

# CACHES AND LIMITS #
tmp-table-size = 32M
max-heap-table-size = 32M
query-cache-type = 0
query-cache-size = 0
max-connections = 500
thread-cache-size = 50
open-files-limit = 65535
table-definition-cache = 1024
table-open-cache = 2048

# INNODB #
innodb-flush-method = O_DIRECT
innodb-log-files-in-group = 2
innodb-log-file-size = 512M
innodb-flush-log-at-trx-commit = 1
innodb-file-per-table = 1
innodb-buffer-pool-size = 20G

# LOGGING #
log-error = /var/lib/mysql/mysql-error.log
log-queries-not-using-indexes = 1
slow-query-log = 1
slow-query-log-file = /var/lib/mysql/mysql-slow.log

Is a bug¿?

Thanks!

2

From documentation:

Sometimes the “during query” form happens when millions of rows are being sent as part of one or more queries. If you know that this is happening, you should try increasing net_read_timeout from its default of 30 seconds to 60 seconds or longer, sufficient for the data transfer to complete.

For Further reading here is documentation link:

[URL]https://dev.mysql.com/doc/refman/5.6/en/error-lost-connection.html[/URL]