Bug #45691 | InnoDB hangs getting foreign key info | ||
---|---|---|---|
Submitted: | 23 Jun 2009 20:40 | Modified: | 24 Jun 2009 17:04 |
Reporter: | Matthew Lord | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
Version: | 5.1.36 | OS: | HP/UX (11.31 on IA64) |
Assigned to: | CPU Architecture: | Any | |
Tags: | hang, hpux, IA64 |
[23 Jun 2009 20:40]
Matthew Lord
[24 Jun 2009 17:04]
Matthew Lord
It looks like the cause is the first critical bug listed here as part of the PHCO_38050 patch set: http://www13.itrc.hp.com/service/patch/patchDetail.do?BC=main|patchDetail{PHCO_38050,{hpux... Based on the debugging that I've done with gdb I can see that the hangs are occurring in the pthread library when InnoDB is doing an ABORT which fits perfectly with HP's description of the bug: PHCO_38050: ABORT HANG Pthread cancel signal is getting consumed by other routine. This will prevent the delivery of the signal to the target thread and the target thread does not exit, subsequently the application hangs. Multithreaded applications that access TLS data types that are 16 bytes in size sometimes get alignment trap.
[24 Jun 2009 17:13]
Matthew Lord
I would recommend that ALL of the following patchsets from HP be installed: PHKL_37465 1.0 thread level enhancements patch PHKL_37457 1.0 thread level signal enhancements patch PHCO_38050 1.0 pthread library cumulative patch PHCO_38048 1.0 libc cumulative patch PHCO_38044 1.0 libc cumulative header file patch PHCO_37128 1.0 libc manpage cumulative patch