slave crash due to cascading foreign key constraint
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
Fix Released
|
High
|
Seppo Jaakola | ||
5.5 |
Fix Released
|
High
|
Seppo Jaakola |
Bug Description
120614 15:25:55 [ERROR] Slave SQL: Could not execute Delete_rows event on table pa.AreaType; Cannot delete or update a parent row: a foreign key constraint fails (`pa`.`Area`, CONSTRAINT `fk_Area_AreaType` FOREIGN KEY (`areaTypeId`) REFERENCES `AreaType` (`id`) ON UPDATE CASCADE), Error_code: 1451; handler error HA_ERR_
120614 15:25:55 [Warning] WSREP: RBR event 2 Delete_rows apply warning: 152, 1925
120614 15:25:55 [ERROR] WSREP: Failed to apply trx: source: 938778e1-
120614 15:25:55 [ERROR] WSREP: Failed to apply app buffer: cæÙO, seqno: 1925, status: WSREP_FATAL
120614 15:28:23 [Warning] WSREP: Certification failed for TO isolated action: source: 938778e1-
120614 15:28:23 [Warning] WSREP: Certification failed for TO isolated action: source: 938778e1-
120614 15:28:23 [Warning] WSREP: Certification failed for TO isolated action: source: 938778e1-
An effective regression test has been implemented for this.
Bug will surface if parent table has non-unique key in the column which is referenced from the child table and slave node has configuration with parallel applying.