Donor Node Crash when Re-joining After Brief Disconnect on Solaris
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Galera |
New
|
Undecided
|
Unassigned | ||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
2014-03-04 03:36:30 92137 [Note] WSREP: Node 0.0 (node2) requested state transfer from 'node1'. Selected 1.0 (node1)(SYNCED) as donor.
2014-03-04 03:36:30 92137 [Note] WSREP: Shifting SYNCED -> DONOR/DESYNCED (TO: 365188155)
03:36:30 UTC - mysqld got signal 11 ;
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:/
key_buffer_
read_buffer_
max_used_
max_threads=5002
thread_count=1912
connection_
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: 0x2a64f1560
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...
/mysql/
/mysql/
/lib/amd64/
/lib/amd64/
/lib/amd64/
/lib/amd64/
/mysql/
/mysql/
/mysql/
/mysql/
/mysql/
/mysql/
/mysql/
/lib/amd64/
/lib/amd64/
Please read http://
and follow instructions on how to resolve the stack trace.
Resolved stack trace is much more helpful in diagnosing the
problem, so please do resolve it
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): 16
Status: NOT_KILLED
You may download the Percona XtraDB Cluster operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
Writing a core file
Changed in percona-xtradb-cluster: | |
status: | New → Incomplete |
How to reproduce (not consistent but at least happened twice), cut off node2 from the cluster via iptables/ipfilter for about 60seconds or so. Then let it reconnect and IST, the crash happens. I've tried to reproduce this on CentOS RPMs to no avail.
mysql> show global variables like '%version%'; ------- ------- -----+- ------- ------- ------- ------- ------- ---+ ------- ------- -----+- ------- ------- ------- ------- ------- ---+ conversions | | compile_ machine | x86_64 | ------- ------- -----+- ------- ------- ------- ------- ------- ---+
+------
| Variable_name | Value |
+------
| innodb_version | 5.6.15-60.3 |
| protocol_version | 10 |
| slave_type_
| version | 5.6.15-log |
| version_comment | Source distribution, wsrep_25.4.rXXXX |
| version_
| version_compile_os | solaris11 |
+------
7 rows in set (0.00 sec)