<?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: Drilling down to the source of the problem</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2008/11/08/drilling-down-to-the-source-of-the-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2008/11/08/drilling-down-to-the-source-of-the-problem/</link>
	<description>Everything about MySQL Performance</description>
	<lastBuildDate>Sat, 07 Nov 2009 18:35:44 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Yasufumi</title>
		<link>http://www.mysqlperformanceblog.com/2008/11/08/drilling-down-to-the-source-of-the-problem/comment-page-1/#comment-381807</link>
		<dc:creator>Yasufumi</dc:creator>
		<pubDate>Sat, 15 Nov 2008 18:18:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=527#comment-381807</guid>
		<description>Davy,

I succeeded to reproduce the problem you met. I think it is MySQL&#039;s bug. I have posted the bug report.

http://bugs.mysql.com/bug.php?id=40760</description>
		<content:encoded><![CDATA[<p>Davy,</p>
<p>I succeeded to reproduce the problem you met. I think it is MySQL&#8217;s bug. I have posted the bug report.</p>
<p><a href="http://bugs.mysql.com/bug.php?id=40760" rel="nofollow">http://bugs.mysql.com/bug.php?id=40760</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2008/11/08/drilling-down-to-the-source-of-the-problem/comment-page-1/#comment-378985</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Fri, 14 Nov 2008 18:46:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=527#comment-378985</guid>
		<description>No. I mean in SHOW INNODB STATUS:

1 queries inside InnoDB, 0 queries in queue
1 read views open inside InnoDB


Sometimes when you check it online the number of &quot;queries inside innodb&quot; will stuck on 1 or something because MySQL will simply stop counting the queries entering/exiting the queue.</description>
		<content:encoded><![CDATA[<p>No. I mean in SHOW INNODB STATUS:</p>
<p>1 queries inside InnoDB, 0 queries in queue<br />
1 read views open inside InnoDB</p>
<p>Sometimes when you check it online the number of &#8220;queries inside innodb&#8221; will stuck on 1 or something because MySQL will simply stop counting the queries entering/exiting the queue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davy Campano</title>
		<link>http://www.mysqlperformanceblog.com/2008/11/08/drilling-down-to-the-source-of-the-problem/comment-page-1/#comment-378855</link>
		<dc:creator>Davy Campano</dc:creator>
		<pubDate>Fri, 14 Nov 2008 17:24:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=527#comment-378855</guid>
		<description>Peter,

Thanks for the response.  I changed the value online.  When you say counting transactions, do you mean queries like the one below?  This is one of the main queries that I saw that was stuck:

SELECT @rank:=@rank-1 AS rank, a.user_id, a.card_id, b.user_name, b.image_url FROM game_winners a 
									INNER JOIN users b ON a.user_id = b.user_id WHERE a.game_id = 5 ORDER BY a.win_time DESC LIMIT 16;</description>
		<content:encoded><![CDATA[<p>Peter,</p>
<p>Thanks for the response.  I changed the value online.  When you say counting transactions, do you mean queries like the one below?  This is one of the main queries that I saw that was stuck:</p>
<p>SELECT @rank:=@rank-1 AS rank, a.user_id, a.card_id, b.user_name, b.image_url FROM game_winners a<br />
									INNER JOIN users b ON a.user_id = b.user_id WHERE a.game_id = 5 ORDER BY a.win_time DESC LIMIT 16;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2008/11/08/drilling-down-to-the-source-of-the-problem/comment-page-1/#comment-378841</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Fri, 14 Nov 2008 17:16:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=527#comment-378841</guid>
		<description>Davy,

Did you restart with zero innodb_thread_concurrency or did you change it online ? 
I&#039;ve seen minor glitches sometimes (even in stick release) changing it online, though I thougth these were only related to counting transactions.

About patch name - it is part of Innodb IO Patches:
	innodb_io_patches.patch</description>
		<content:encoded><![CDATA[<p>Davy,</p>
<p>Did you restart with zero innodb_thread_concurrency or did you change it online ?<br />
I&#8217;ve seen minor glitches sometimes (even in stick release) changing it online, though I thougth these were only related to counting transactions.</p>
<p>About patch name &#8211; it is part of Innodb IO Patches:<br />
	innodb_io_patches.patch</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davy Campano</title>
		<link>http://www.mysqlperformanceblog.com/2008/11/08/drilling-down-to-the-source-of-the-problem/comment-page-1/#comment-378767</link>
		<dc:creator>Davy Campano</dc:creator>
		<pubDate>Fri, 14 Nov 2008 16:19:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=527#comment-378767</guid>
		<description>Also, was curious what is the name of the patch that addresses Innodb fuzzy checkpointing algorithm?  You just linked to the page with all the patches.  Thanks!</description>
		<content:encoded><![CDATA[<p>Also, was curious what is the name of the patch that addresses Innodb fuzzy checkpointing algorithm?  You just linked to the page with all the patches.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davy Campano</title>
		<link>http://www.mysqlperformanceblog.com/2008/11/08/drilling-down-to-the-source-of-the-problem/comment-page-1/#comment-378738</link>
		<dc:creator>Davy Campano</dc:creator>
		<pubDate>Fri, 14 Nov 2008 16:04:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=527#comment-378738</guid>
		<description>Hey Peter,

I had a question about changing innodb_thread_concurrency.  I changed it on a server yesterday from 8 to 0 and it caused the server to lockup.  I am running the hi-perf 5.0.67 release, and I have some tables that use BEFORE INSERT triggers to update another value in a different table.  I was curious if you might have any idea why this would happen.  Here are a couple outputs from my log file when I made the change:

081113 16:41:32  InnoDB: Error: Freeing a trx which is declared to be processing
InnoDB: inside InnoDB.
TRANSACTION 1 2897690526, not started, process no 17811, OS thread id 1197627712, thread declared inside InnoDB 499
MySQL thread id 243641148, query id 2415637111 XX.XX.XX.XX MY_USERNAME

081113 16:41:32  InnoDB: Error: Freeing a trx which is declared to be processing
InnoDB: inside InnoDB.
TRANSACTION 1 2897690560, not started, process no 17811, OS thread id 1196562752, thread declared inside InnoDB 500
MySQL thread id 243641179, query id 2415637163 XX.XX.XX.XX MY_USERNAME

I had 7 of these show up in my logs, and then I had a couple hundred statements show up in processlist that wouldn&#039;t finish.</description>
		<content:encoded><![CDATA[<p>Hey Peter,</p>
<p>I had a question about changing innodb_thread_concurrency.  I changed it on a server yesterday from 8 to 0 and it caused the server to lockup.  I am running the hi-perf 5.0.67 release, and I have some tables that use BEFORE INSERT triggers to update another value in a different table.  I was curious if you might have any idea why this would happen.  Here are a couple outputs from my log file when I made the change:</p>
<p>081113 16:41:32  InnoDB: Error: Freeing a trx which is declared to be processing<br />
InnoDB: inside InnoDB.<br />
TRANSACTION 1 2897690526, not started, process no 17811, OS thread id 1197627712, thread declared inside InnoDB 499<br />
MySQL thread id 243641148, query id 2415637111 XX.XX.XX.XX MY_USERNAME</p>
<p>081113 16:41:32  InnoDB: Error: Freeing a trx which is declared to be processing<br />
InnoDB: inside InnoDB.<br />
TRANSACTION 1 2897690560, not started, process no 17811, OS thread id 1196562752, thread declared inside InnoDB 500<br />
MySQL thread id 243641179, query id 2415637163 XX.XX.XX.XX MY_USERNAME</p>
<p>I had 7 of these show up in my logs, and then I had a couple hundred statements show up in processlist that wouldn&#8217;t finish.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aurimas Mikalauskas</title>
		<link>http://www.mysqlperformanceblog.com/2008/11/08/drilling-down-to-the-source-of-the-problem/comment-page-1/#comment-375772</link>
		<dc:creator>Aurimas Mikalauskas</dc:creator>
		<pubDate>Tue, 11 Nov 2008 11:15:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=527#comment-375772</guid>
		<description>Peter,

thanks - indeed quite an interesting case and makes feel good knowing we have the patch for it :) Also, I didn&#039;t know innodb_thread_concurrency can be changed online - this is useful to experiment with.</description>
		<content:encoded><![CDATA[<p>Peter,</p>
<p>thanks &#8211; indeed quite an interesting case and makes feel good knowing we have the patch for it <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Also, I didn&#8217;t know innodb_thread_concurrency can be changed online &#8211; this is useful to experiment with.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
