Bug #73017 slow MySQL recovery logs "MySQL service hung on starting"

• Submitted: 17 Jun 2014 2:50
• Modified: 17 Jun 2014 2:54
• Reporter: Andrew Dalgleish
• Status: Verified
• Category: MySQL Server: Windows
• Severity: S3 (Non-critical)
• Version: 5.6.15
• OS: Windows
• CPU Architecture: Any

[17 Jun 2014 2:50] Andrew Dalgleish

Description:
If the crash recovery exceeds the Windows Service Control Manager default timeout, the SCM logs "MySQL service hung on starting".
Any dependent services will fail to start.

How to repeat:
Create a large InnoDB datafile crash recovery, then do a not-clean reboot.

Suggested fix:
The mysqld service should pass a monotonically increasing value for dwCheckPoint to SetServiceStatus() during crash recovery.

[17 Jun 2014 2:54] MySQL Verification Team

See the description for dwCheckPoint and dwWaitHint here:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms685996%28v=vs.85%29.aspx

[17 Jun 2014 3:06] MySQL Verification Team

You can set slow-start-timeout, but it is hard to know in advance how large this should be.

[17 Jun 2014 5:17] MySQL Verification Team

related: http://bugs.mysql.com/bug.php?id=45547