non-uniform FK reference can cause slave crash

Bug #1089490 reported by Seppo Jaakola on 2012-12-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Seppo Jaakola
Seppo Jaakola
Percona XtraDB Cluster moved to
Fix Released

Bug Description

Slave node may crash due to foreign key processing problem, if following conditions are met:

1. foreign key constraint has been defined with CASCADE ON DELETE option
2. foreign key constraint has mixed NULL options in referencing columns
  (i.e. client column defined with NOT NULL option and parent column with NULL option)
3. slave is configured with multiple slave threads (wsrep_slave_threads > 1)
4. work load has conflicting DELETE operations for parent and child table

This problem was observed in Percona XtraDB Cluster installation, and reproduced with a regression test in Galera Cluster

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

as a followup fix, in cascading delete processing, suppressing obsolete shared keys for parent table (which has exclusive key appended as well). Fix pushed in wsrep-5.5:

Seppo Jaakola (seppo-jaakola) wrote :

Second followup fix, uses PK of child table when appending exclusive key for cascading delete operation. Fix pushed in wsrep-5.5:

Alex Yurchenko (ayurchen) wrote :

fix released in 23.7.3

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

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