foreign key warnings
Bug #1057910 reported by
Seppo Jaakola
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MySQL patches by Codership |
Fix Released
|
Medium
|
Seppo Jaakola | ||
Bug Description
Some users have reported of foreign key warnings appearing in error log:
WSREP: FK key len exceeded 0 4294967295 3500
[ERROR] WSREP: FK key set failed: 11
WSREP: skipping FK key append
This issue has not been reproduced so far. Code analysis shows that foreign key check will fail if one of the parts in the key has NULL value.
=> improve the log messages for FK issues to show related table and original SQL
=> fix the treatment of NULL value in FK
| Changed in codership-mysql: | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
| milestone: | none → 5.5.27-23.7 |
| status: | In Progress → Fix Committed |
Revision history for this message
| brad svee (brad-svee) wrote | #1 |
| Changed in codership-mysql: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We attempted to upgrade our passive node in our cluster from Percona-
Immediately upon upgrade and restart, it forced an SST because it didn't recognize sequence number -1, and upon re-init the IST ran and it begin spewing just this error:
WSREP: skipping FK key append
Note we did not ever see the other FK key len exceeded error. At our load it generated about 25,000 of these errors in about 5 minutes. We attempted to enable debugging for wsrep and no additional information came out.