non-uniform FK reference can cause slave crash
Bug #1089490 reported by
Seppo Jaakola
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
Fix Released
|
High
|
Seppo Jaakola | ||
5.5 |
Fix Released
|
High
|
Seppo Jaakola | ||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
Fix Released
|
Undecided
|
Unassigned |
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_
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 |
Changed in percona-xtradb-cluster: | |
milestone: | none → 5.5.30-23.7.4 |
status: | New → Fix Released |
To post a comment you must log in.
actual fix pushed in wsrep-5.5 here: http:// bazaar. launchpad. net/~codership/ codership- mysql/wsrep- 5.5/revision/ 3834