Crash when restarting another node

[Rodrigo]

Crash when restarting another node

I am using Percona Cluster 5.6.24-72.2-56-log running in Centos 6.5 ( 2.6.32-431.3.1.el6.x86_64 )

Three nodes: n1,n2,n3

I restarted n3.
n1 started doing an SST (IST?) and crashed. n3 failed to restart. n2 is Initialized mode.

Extra info:
n1 is using native mysql replication as well with another server (unaffected).

n1 is vmware box with 32GB of ram

the gache is 4GB
innodb_buffer_pool_size = 8G
innodb_buffer_pool_instances = 8
innodb_log_buffer_size = 64M
innodb_log_file_size = 2000M

I have a core file but it's pretty huge: 11GB

[Rodrigo (rodri-bernardo)]

The stack trace:
2015-09-22 12:19:25 57535 [Note] WSREP: save pc into disk
2015-09-22 12:19:25 57535 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 0, memb_num = 3
2015-09-22 12:19:25 57535 [Note] WSREP: STATE_EXCHANGE: sent state UUID: c850de5b-611b-11e5-953f-9a742127fd75
2015-09-22 12:19:25 57535 [Note] WSREP: STATE EXCHANGE: sent state msg: c850de5b-611b-11e5-953f-9a742127fd75
2015-09-22 12:19:25 57535 [Note] WSREP: STATE EXCHANGE: got state msg: c850de5b-611b-11e5-953f-9a742127fd75 from 0 (pcluster1)
2015-09-22 12:19:25 57535 [Note] WSREP: STATE EXCHANGE: got state msg: c850de5b-611b-11e5-953f-9a742127fd75 from 2 (pcluster2)
2015-09-22 12:19:26 57535 [Note] WSREP: STATE EXCHANGE: got state msg: c850de5b-611b-11e5-953f-9a742127fd75 from 1 (pcluster3)
2015-09-22 12:19:26 57535 [Note] WSREP: Quorum results:
 version = 3,
 component = PRIMARY,
 conf_id = 38,
 members = 2/3 (joined/total),
 act_id = 25331890,
 last_appl. = 25331804,
 protocols = 0/7/3 (gcs/repl/appl),
 group UUID = f51b58f0-5c96-11e5-aa40-c320e9a6ab00
2015-09-22 12:19:26 57535 [Note] WSREP: Flow-control interval: [28, 28]
2015-09-22 12:19:26 57535 [Note] WSREP: New cluster view: global state: f51b58f0-5c96-11e5-aa40-c320e9a6ab00:25331890, view# 39: Primary, number of nodes: 3, my index: 0, protocol version 3
2015-09-22 12:19:26 57535 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2015-09-22 12:19:26 57535 [Note] WSREP: REPL Protocols: 7 (3, 2)
2015-09-22 12:19:26 57535 [Note] WSREP: Service thread queue flushed.
2015-09-22 12:19:26 57535 [Note] WSREP: Assign initial position for certification: 25331890, protocol version: 3
2015-09-22 12:19:26 57535 [Note] WSREP: Service thread queue flushed.
2015-09-22 12:19:27 57535 [Note] WSREP: Member 1.0 (pcluster3) requested state transfer from '*any*'. Selected 0.0 (pcluster1)(SYNCED) as donor.
2015-09-22 12:19:27 57535 [Note] WSREP: Shifting SYNCED -> DONOR/DESYNCED (TO: 25332221)
2015-09-22 12:19:27 57535 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2015-09-22 12:19:27 57535 [Note] WSREP: Running: 'wsrep_sst_xtrabackup-v2 --role 'donor' --address 'pcluster3:4444/xtrabackup_sst//1' --auth 'sst:sst' --socket '/var/lib/mysql/mysql.sock' --datadir '/var/lib/mysql/' --defaults-file '/etc/my.cnf' --defaults-group-suffix '' '' --gtid 'f51b58f0-5c96-11e5-aa40-c320e9a6ab00:25332221''
terminate called after throwing an instance of 'St9bad_alloc'
  what(): std::bad_alloc
11:19:27 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://bugs.launchpad.net/percona-xtradb-cluster

key_buffer_size=2147483648
read_buffer_size=131072
max_used_connections=5
max_threads=5002
thread_count=6
connection_count=2
It is possib...

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1856