Cluster Failure after Online Schema Upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hello ,
Percona Xtra DB Cluster (5.6.30-76.3-56) wholw cluster failed after RSU action. I have 5 nodes in my cluster. I am listing below all steps.
I was adding new column to a table using rolling schema upgrade. Everything was fine and I have done same procedure before many times.
the steps are below. I applied these steps to my three nodes and all three nodes are ok. But on 4. node I applied step 8 and firstly Node4 crashed. After 10 15 seconds whole cluster failed. I am sharing success node log and failed node log bottom,
1.) disable node on load balancer and wait for active connections to end
2.) SET GLOBAL wsrep_OSU_
3.) SET GLOBAL wsrep_slave_
4.) SET GLOBAL foreign_
5.) SET foreign_
6.) SET GLOBAL wsrep_cluster_
7.) ALTER TABLE tablename ADD COLUMN columnname VARCHAR(4) DEFAULT '';
8.) SET GLOBAL wsrep_cluster_
9.) SET foreign_
10.)SET GLOBAL foreign_
11.)SET GLOBAL wsrep_slave_
12.)SET GLOBAL wsrep_OSU_
13.)enable node on load balancer
After failure I bootstrapped most advanced node and activated cluster again. it says that mysqld got signal 11 . But I have no idea about this failure and why whole cluster failed instead of failed node. is it a bug? maybe I am missing something. help please
Success node logs are below after step 8 applied:
2017-11-01 16:12:24 3157 [Note] WSREP: GMCast version 0
2017-11-01 16:12:24 3157 [Note] WSREP: (4d5ca708, 'tcp://
2017-11-01 16:12:24 3157 [Note] WSREP: (4d5ca708, 'tcp://
2017-11-01 16:12:24 3157 [Note] WSREP: EVS version 0
2017-11-01 16:12:24 3157 [Note] WSREP: gcomm: connecting to group 'my_wsrep_cluster', peer 'xxx.23.
2017-11-01 16:12:24 3157 [Warning] WSREP: (4d5ca708, 'tcp://
2017-11-01 16:12:24 3157 [Note] WSREP: (4d5ca708, 'tcp://
2017-11-01 16:12:25 3157 [Note] WSREP: declaring 6268fd11 at tcp://xxx.
2017-11-01 16:12:25 3157 [Note] WSREP: declaring f0346ac8 at tcp://xxx.
2017-11-01 16:12:25 3157 [Note] WSREP: declaring f87ad44d at tcp://xxx.
2017-11-01 16:12:25 3157 [Note] WSREP: Node 6268fd11 state prim
2017-11-01 16:12:25 3157 [Note] WSREP: view(view_
4d5ca708,0
6268fd11,0
f0346ac8,0
f87ad44d,0
} joined {
} left {
} partitioned {
})
2017-11-01 16:12:25 3157 [Note] WSREP: save pc into disk
2017-11-01 16:12:25 3157 [Note] WSREP: discarding pending addr without UUID: tcp://xxx.
2017-11-01 16:12:26 3157 [Note] WSREP: gcomm: connected
2017-11-01 16:12:26 3157 [Note] WSREP: Changing maximum packet size to 64500, resulting msg size: 32636
2017-11-01 16:12:26 3157 [Note] WSREP: Shifting CLOSED -> OPEN (TO: 3691602)
2017-11-01 16:12:26 3157 [Note] WSREP: Opened channel 'my_wsrep_cluster'
2017-11-01 16:12:26 3157 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 0, memb_num = 4
2017-11-01 16:12:26 3157 [Note] WSREP: STATE_EXCHANGE: sent state UUID: 4e475f33-
2017-11-01 16:12:26 3157 [Note] WSREP: STATE EXCHANGE: sent state msg: 4e475f33-
2017-11-01 16:12:26 3157 [Note] WSREP: STATE EXCHANGE: got state msg: 4e475f33-
2017-11-01 16:12:26 3157 [Note] WSREP: STATE EXCHANGE: got state msg: 4e475f33-
2017-11-01 16:12:26 3157 [Note] WSREP: STATE EXCHANGE: got state msg: 4e475f33-
2017-11-01 16:12:26 3157 [Note] WSREP: STATE EXCHANGE: got state msg: 4e475f33-
2017-11-01 16:12:26 3157 [Note] WSREP: Quorum results:
version = 4,
component = PRIMARY,
conf_id = 676,
members = 3/4 (joined/total),
act_id = 3691645,
last_appl. = 3691483,
protocols = 0/7/3 (gcs/repl/appl),
group UUID = 8c54c159-
2017-11-01 16:12:26 3157 [Note] WSREP: Flow-control interval: [32, 32]
2017-11-01 16:12:26 3157 [Note] WSREP: Shifting OPEN -> PRIMARY (TO: 3691645)
2017-11-01 16:12:26 3157 [Note] WSREP: State transfer required:
Group state: 8c54c159-
Local state: 8c54c159-
2017-11-01 16:12:26 3157 [Note] WSREP: New cluster view: global state: 8c54c159-
2017-11-01 16:12:26 3157 [Warning] WSREP: Gap in state sequence. Need state transfer.
2017-11-01 16:12:26 3157 [Note] WSREP: You have configured 'xtrabackup-v2' state snapshot transfer method which cannot be performed on a running server. Wsrep provider won't be able to fall back to it if other means of state transfer are unavailable. In that case you will need to restart the server.
2017-11-01 16:12:26 3157 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2017-11-01 16:12:26 3157 [Note] WSREP: REPL Protocols: 7 (3, 2)
2017-11-01 16:12:26 3157 [Note] WSREP: Service thread queue flushed.
2017-11-01 16:12:26 3157 [Note] WSREP: Assign initial position for certification: 3691645, protocol version: 3
2017-11-01 16:12:26 3157 [Note] WSREP: Service thread queue flushed.
2017-11-01 16:12:26 3157 [Note] WSREP: IST receiver addr using tcp://xxx.
2017-11-01 16:12:26 3157 [Note] WSREP: Prepared IST receiver, listening at: tcp://xxx.
2017-11-01 16:12:26 3157 [Note] WSREP: Member 0.0 (xxx.23.yyy.103) requested state transfer from '*any*'. Selected 3.0 (xxx.17.
2017-11-01 16:12:26 3157 [Note] WSREP: Shifting PRIMARY -> JOINER (TO: 3691647)
2017-11-01 16:12:26 3157 [Note] WSREP: Requesting state transfer: success, donor: 3
2017-11-01 16:12:26 3157 [Note] WSREP: Receiving IST: 43 writesets, seqnos 3691602-3691645
2017-11-01 16:12:26 3157 [Note] WSREP: 3.0 (xxx.17.yyy.101): State transfer to 0.0 (xxx.23.yyy.103) complete.
2017-11-01 16:12:26 3157 [Note] WSREP: Member 3.0 (xxx.17.yyy.101) synced with group.
2017-11-01 16:12:26 3157 [Note] WSREP: IST received: 8c54c159-
2017-11-01 16:12:26 3157 [Note] WSREP: 0.0 (xxx.23.yyy.103): State transfer from 3.0 (xxx.17.yyy.101) complete.
2017-11-01 16:12:26 3157 [Note] WSREP: Shifting JOINER -> JOINED (TO: 3691647)
2017-11-01 16:12:26 3157 [Note] WSREP: Member 0.0 (xxx.23.yyy.103) synced with group.
2017-11-01 16:12:26 3157 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 3691647)
2017-11-01 16:12:26 3157 [Note] WSREP: Synchronized with group, ready for connections
And failed node logs are below after step 8 applied:
2017-11-01 16:22:10 3120 [Note] WSREP: GMCast version 0
2017-11-01 16:22:10 3120 [Note] WSREP: (aa8776f3, 'tcp://
2017-11-01 16:22:10 3120 [Note] WSREP: (aa8776f3, 'tcp://
2017-11-01 16:22:10 3120 [Note] WSREP: EVS version 0
2017-11-01 16:22:10 3120 [Note] WSREP: gcomm: connecting to group 'my_wsrep_cluster', peer 'xxx.23.
2017-11-01 16:22:10 3120 [Warning] WSREP: (aa8776f3, 'tcp://
2017-11-01 16:22:10 3120 [Note] WSREP: (aa8776f3, 'tcp://
2017-11-01 16:22:11 3120 [Note] WSREP: declaring 4d5ca708 at tcp://xxx.
2017-11-01 16:22:11 3120 [Note] WSREP: declaring 6268fd11 at tcp://xxx.
2017-11-01 16:22:11 3120 [Note] WSREP: declaring f87ad44d at tcp://xxx.
2017-11-01 16:22:11 3120 [Note] WSREP: Node 4d5ca708 state prim
2017-11-01 16:22:11 3120 [Note] WSREP: view(view_
4d5ca708,0
6268fd11,0
aa8776f3,0
f87ad44d,0
} joined {
} left {
} partitioned {
})
2017-11-01 16:22:11 3120 [Note] WSREP: save pc into disk
2017-11-01 16:22:11 3120 [Note] WSREP: discarding pending addr without UUID: tcp://xxx.
2017-11-01 16:22:11 3120 [Note] WSREP: gcomm: connected
2017-11-01 16:22:11 3120 [Note] WSREP: Changing maximum packet size to 64500, resulting msg size: 32636
2017-11-01 16:22:11 3120 [Note] WSREP: Shifting CLOSED -> OPEN (TO: 3691718)
2017-11-01 16:22:11 3120 [Note] WSREP: Opened channel 'my_wsrep_cluster'
2017-11-01 16:22:11 3120 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 2, memb_num = 4
13:22:11 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=202
thread_count=9
connection_count=7
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: 0x2b5e200
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 = 7fab140a8d38 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fa90408c2a0): is an invalid pointer
Connection ID (thread ID): 8853541
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.
171101 16:22:11 mysqld_safe Number of processes running now: 0
171101 16:22:11 mysqld_safe WSREP: not restarting wsrep node automatically
171101 16:22:11 mysqld_safe mysqld from pid file /var/lib/
Changed in percona-xtradb-cluster: | |
status: | New → Invalid |
I assume you are hitting this bug https:/ /jira.percona. com/browse/ PXC-601.
Bug was regression introduced in 5.6.30 and was fixed in 5.6.32.
I would recommend you to re-try this with latest PXC 5.6.37. If you still hit the issue we would be happy to investigate it further.