mysqldump error not propagated to SST script caller

Bug #884183 reported by Teemu Ollakka on 2011-10-31
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Medium
Teemu Ollakka
5.1
Medium
Teemu Ollakka
5.5
Medium
Teemu Ollakka

Bug Description

Installing 5.1 using 5.5 databases revealed the following issue:

111031 13:06:23 [Note] WSREP: New cluster view: global state: f5f2148b-03ab-11e1-0800-8edb
4a8b2e2b:0, view# 3: Primary, number of nodes: 3, my index: 0, protocol version 1
111031 13:06:23 [Warning] WSREP: wsrep_notify_cmd is not defined, skipping notification.
111031 13:06:23 [Note] WSREP: Assign initial position for certification: 0, protocol versi
on: 1
111031 13:06:24 [Note] WSREP: Node 2 (test2) requested state transfer from '*any*'. Select
ed 0 (test1)(SYNCED) as donor.
111031 13:06:24 [Note] WSREP: Got GCS_ACT_STATE_REQ to 0, my idx: 0
111031 13:06:24 [Note] WSREP: Shifting SYNCED -> DONOR (TO: 0)
111031 13:06:24 [Warning] WSREP: wsrep_notify_cmd is not defined, skipping notification.
mysqldump: Couldn't execute 'show create table `cond_instances`': Unknown table engine 'PE
RFORMANCE_SCHEMA' (1286)
111031 13:06:26 [Note] WSREP: 0 (test1): State transfer to 2 (test2) complete.
111031 13:06:26 [Note] WSREP: Shifting DONOR -> JOINED (TO: 0)
111031 13:06:26 [Note] WSREP: Member 0 (test1) synced with group.
111031 13:06:26 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 0)

mysqldump failed to dump database on DONOR due to incompatibility, but script didn't return error to caller. Because initial position was not sent to JOINER and DONOR didn't report any error, JOINER was left hanging in "Waiting for SST (4)".

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers