<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to decrease InnoDB shutdown times</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/</link>
	<description>Percona&#039;s MySQL &#38; InnoDB performance and scalability blog</description>
	<lastBuildDate>Sat, 11 Feb 2012 16:45:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Andy Blyler</title>
		<link>http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/comment-page-1/#comment-780405</link>
		<dc:creator>Andy Blyler</dc:creator>
		<pubDate>Wed, 27 Oct 2010 12:07:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=660#comment-780405</guid>
		<description>You can also execute the following SQL query to get the current count of the dirty pool pages, instead of using mysqladmin:

     show global status like &#039;Innodb_buffer_pool_pages_dirty&#039;;</description>
		<content:encoded><![CDATA[<p>You can also execute the following SQL query to get the current count of the dirty pool pages, instead of using mysqladmin:</p>
<p>     show global status like &#8216;Innodb_buffer_pool_pages_dirty&#8217;;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wagner Bianchi</title>
		<link>http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/comment-page-1/#comment-773819</link>
		<dc:creator>Wagner Bianchi</dc:creator>
		<pubDate>Fri, 10 Sep 2010 19:02:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=660#comment-773819</guid>
		<description>Sorry, *Take care</description>
		<content:encoded><![CDATA[<p>Sorry, *Take care</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wagner Bianchi</title>
		<link>http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/comment-page-1/#comment-773818</link>
		<dc:creator>Wagner Bianchi</dc:creator>
		<pubDate>Fri, 10 Sep 2010 19:02:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=660#comment-773818</guid>
		<description>Take when issue a KILL -9 command against mysqld. If MySQL is answering any writes on any MyISAM tables, you&#039;ll see problems that would be repaired.</description>
		<content:encoded><![CDATA[<p>Take when issue a KILL -9 command against mysqld. If MySQL is answering any writes on any MyISAM tables, you&#8217;ll see problems that would be repaired.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coway Zhou</title>
		<link>http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/comment-page-1/#comment-773808</link>
		<dc:creator>Coway Zhou</dc:creator>
		<pubDate>Fri, 10 Sep 2010 17:17:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=660#comment-773808</guid>
		<description>I tried it once. But it never worked. I lost patient and did a kill -9. Of course, when the db was started, it did long time in recovery. At least it showed some progress in recovery.</description>
		<content:encoded><![CDATA[<p>I tried it once. But it never worked. I lost patient and did a kill -9. Of course, when the db was started, it did long time in recovery. At least it showed some progress in recovery.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kerja keras</title>
		<link>http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/comment-page-1/#comment-666392</link>
		<dc:creator>kerja keras</dc:creator>
		<pubDate>Mon, 19 Oct 2009 03:39:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=660#comment-666392</guid>
		<description>great tips, its very helpful. thanks for share</description>
		<content:encoded><![CDATA[<p>great tips, its very helpful. thanks for share</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Baron Schwartz</title>
		<link>http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/comment-page-1/#comment-561186</link>
		<dc:creator>Baron Schwartz</dc:creator>
		<pubDate>Thu, 14 May 2009 17:36:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=660#comment-561186</guid>
		<description>Kayra, it can become negative because the insert buffer survives after restart and merging can continue after the server is started again.  Peter tells me he has seen servers take weeks to catch up in some cases!</description>
		<content:encoded><![CDATA[<p>Kayra, it can become negative because the insert buffer survives after restart and merging can continue after the server is started again.  Peter tells me he has seen servers take weeks to catch up in some cases!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kayra Otaner</title>
		<link>http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/comment-page-1/#comment-561178</link>
		<dc:creator>Kayra Otaner</dc:creator>
		<pubDate>Thu, 14 May 2009 16:16:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=660#comment-561178</guid>
		<description>Even after all the updating threads shut down, you&#039;ll see Innodb_buffer_pool_pages_dirty count approaching to 0 but still increasing sometimes. This is because of InnoDB merges, you can observe this using &#039;show engine innodb status\G&#039;. Only when all the merges are completed pages_dirty count will be 0 and stay at zero. To calculate how many merges still need to be done :
Under &quot;INSERT BUFFER AND ADAPTIVE HASH INDEX&quot; section difference between &#039;Inserts&#039; and &#039;merged recs&#039; will show how many to go. Example :

-------------------------------------
INSERT BUFFER AND ADAPTIVE HASH INDEX
-------------------------------------
Ibuf: size 4185, free list len 3748, seg size 7934,
65171060 inserts, 65171060 merged recs, 10552858 merges
Hash table size 7055701, used cells 32410, node heap has 33 buffer(s)

65171060 - 65171060 = 0

this means that Innodb_buffer_pool_pages_dirty should be 0 and stay at 0. Please note this calculation works most of the time, but sometimes &#039;inserts&#039; - &#039;merged recs&#039; value goes negative values.</description>
		<content:encoded><![CDATA[<p>Even after all the updating threads shut down, you&#8217;ll see Innodb_buffer_pool_pages_dirty count approaching to 0 but still increasing sometimes. This is because of InnoDB merges, you can observe this using &#8216;show engine innodb status\G&#8217;. Only when all the merges are completed pages_dirty count will be 0 and stay at zero. To calculate how many merges still need to be done :<br />
Under &#8220;INSERT BUFFER AND ADAPTIVE HASH INDEX&#8221; section difference between &#8216;Inserts&#8217; and &#8216;merged recs&#8217; will show how many to go. Example :</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
INSERT BUFFER AND ADAPTIVE HASH INDEX<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
Ibuf: size 4185, free list len 3748, seg size 7934,<br />
65171060 inserts, 65171060 merged recs, 10552858 merges<br />
Hash table size 7055701, used cells 32410, node heap has 33 buffer(s)</p>
<p>65171060 &#8211; 65171060 = 0</p>
<p>this means that Innodb_buffer_pool_pages_dirty should be 0 and stay at 0. Please note this calculation works most of the time, but sometimes &#8216;inserts&#8217; &#8211; &#8216;merged recs&#8217; value goes negative values.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wagner Bianchi</title>
		<link>http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/comment-page-1/#comment-542369</link>
		<dc:creator>Wagner Bianchi</dc:creator>
		<pubDate>Sat, 18 Apr 2009 01:47:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=660#comment-542369</guid>
		<description>This is a very good idea.
So nice.</description>
		<content:encoded><![CDATA[<p>This is a very good idea.<br />
So nice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Burton</title>
		<link>http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/comment-page-1/#comment-541960</link>
		<dc:creator>Kevin Burton</dc:creator>
		<pubDate>Fri, 17 Apr 2009 16:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=660#comment-541960</guid>
		<description>Another note... we have three replicas of everything.

When we restart an InnoDB box it is taken out of production and does not serve requests.

Then we flush the innodb buffer pools, then restart it.

The script I linked to above is just added as a one liner to our /etc/init.d/mysql script.... if InnoDB isn&#039;t running on this box it isn&#039;t run.  

We have about 1/2 of our cluster on MyISAM without InnoDB enabled so this would break otherwise.</description>
		<content:encoded><![CDATA[<p>Another note&#8230; we have three replicas of everything.</p>
<p>When we restart an InnoDB box it is taken out of production and does not serve requests.</p>
<p>Then we flush the innodb buffer pools, then restart it.</p>
<p>The script I linked to above is just added as a one liner to our /etc/init.d/mysql script&#8230;. if InnoDB isn&#8217;t running on this box it isn&#8217;t run.  </p>
<p>We have about 1/2 of our cluster on MyISAM without InnoDB enabled so this would break otherwise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Burton</title>
		<link>http://www.mysqlperformanceblog.com/2009/04/15/how-to-decrease-innodb-shutdown-times/comment-page-1/#comment-541959</link>
		<dc:creator>Kevin Burton</dc:creator>
		<pubDate>Fri, 17 Apr 2009 16:49:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=660#comment-541959</guid>
		<description>Hey Baron.... 

Here&#039;s the script we&#039;re using:

http://pastebin.com/f5ec2f70d

If we were to write it again it would almost certainly be written in python.

Kevin</description>
		<content:encoded><![CDATA[<p>Hey Baron&#8230;. </p>
<p>Here&#8217;s the script we&#8217;re using:</p>
<p><a href="http://pastebin.com/f5ec2f70d" rel="nofollow">http://pastebin.com/f5ec2f70d</a></p>
<p>If we were to write it again it would almost certainly be written in python.</p>
<p>Kevin</p>
]]></content:encoded>
	</item>
</channel>
</rss>

