Bug #45414 long shut down with high InnoDB dirty pages
Submitted: 9 Jun 2009 20:06
Reporter: Kyle Joiner Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server Severity:S4 (Feature request)
Version: OS:Any
Assigned to: CPU Architecture:Any
Tags: dirty pages, innodb, shutdown

[9 Jun 2009 20:06] Kyle Joiner
Description:
shutting down with a long wait for InnoDB:

That was a shutdown with 61000 dirty pages. During the shutdown the database cannot be touched at all, it cannot even be monitored to check the progress of the shutdown.

The better way to handle that is to modify safe_mysqld to 'set innodb_dirty_pages_pct = 0' and check the number of dirty pages until the number is a 3 digit number, and only then actually do the shutdown.

How to repeat:
Create large number of dirty pages and immediately shutdown

Suggested fix:
The better way to handle that is to modify safe_mysqld to 'set innodb_dirty_pages_pct = 0' and check the number of dirty pages until the number is a 3 digit number, and only then actually do the shutdown.