Slave thread crash during FK checking
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
Fix Released
|
Medium
|
Seppo Jaakola |
Bug Description
PXC 5.5.30 node crashed with following trace:
Thread pointer: 0x7fc28c000990
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7fc2fbb26db8 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/sbin/
/usr/sbin/
/lib64/
The upper innodb part was resolved as:
0x8df0bc lock_number_
0x84a967 trx_print + 327
0x91b61b row_ins_
0x91c28f row_ins_
0x824863 wsrep_row_
0x825665 row_upd_
0x8268fa row_upd_step + 906
0x80e816 row_update_
0x91ab2c row_ins_
0x91bf9b row_ins_
0x824dc3 row_upd_
0x8260fc row_upd_clust_step + 2476
0x826741 row_upd_step + 465
0x811611 row_update_
0x7ed68f _ZN11ha_
Probable cause for this crash is inconsistency that was introduced with earlier DDL operations. However, this stack trace shows that slave applier does excessive foreign key checks, which should be optimized out.
Changed in codership-mysql: | |
importance: | Undecided → Medium |
assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
milestone: | none → 5.5.32-23.7.6 |
Changed in codership-mysql: | |
status: | Fix Committed → Fix Released |
Fix for skipping FK parent row tracking in replication slave processing was pushed in as part of 5.5.32 merge: http:// bazaar. launchpad. net/~codership/ codership- mysql/5. 5-23/revision/ 3894
The actual patch is in storage/ innobase/ row0upd. c
But, this patch needs some fixing to be buildable, here is the last commit for this issue: http:// bazaar. launchpad. net/~codership/ codership- mysql/5. 5-23/revision/ 3896