cascading FK constraint can cause slave hanging

Bug #1130888 reported by Seppo Jaakola on 2013-02-20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Seppo Jaakola
Seppo Jaakola
Percona XtraDB Cluster moved to
Fix Released

Bug Description

Replication of a delete on table which is referenced by cascading foreign key constraint can interfere with a write on the child table and under certain conditions this can lead to unresolved replication conflict. As a result the slave thread can remain hanging.

A separate regression test has been created for this issue.

Related branches

Changed in codership-mysql:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Seppo Jaakola (seppo-jaakola)
milestone: none → 5.5.29-23.7.3
Seppo Jaakola (seppo-jaakola) wrote :

Problem was introduced by wsrep originated FK checks for referenced table, which did not check the possible deadlock error happening during the FK checking

Seppo Jaakola (seppo-jaakola) wrote :

The fix revision was wrong in the comment above, correct fix revision is:

Changed in percona-xtradb-cluster:
milestone: none → 5.5.30-23.7.4
status: New → Fix Released

Will this fix be applied in 5.6? I believe this could have caused a deadlock which lead to this bug:

vineet khanna (khannavin) wrote :

Please confirm If this bug is not affecting 5.6?

Percona now uses JIRA for bug reports so this bug report is migrated to:

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

Other bug subscribers