<?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: Simple MySQL Proxy Failover</title>
	<atom:link href="http://www.pythian.com/news/896/simple-mysql-proxy-failover/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news/896/simple-mysql-proxy-failover/</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Fri, 10 Feb 2012 13:01:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: val</title>
		<link>http://www.pythian.com/news/896/simple-mysql-proxy-failover/#comment-434043</link>
		<dc:creator>val</dc:creator>
		<pubDate>Sat, 05 Jun 2010 05:55:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/896/simple-mysql-proxy-failover#comment-434043</guid>
		<description>I&#039;m having an issue using this script. I have my setup as two mysqld servers with master-master replication. When I unplug the network cable to master1 the mysql-proxy takes 3 minutes to failover to master2 and only marks master1 into state=2 (down) for 4 seconds. Then it &#039;wakes it up&#039; again to state=0 (unknown). Upon the next query it takes another 3 minutes to fail (3 minutes because of the tcp timeout?) back to state=2 and then the whole cycle stars over again.

Why would it try to wake up the master1 after 4 seconds? What if the master1 machine goes down for the entire night, shouldn&#039;t it just keep it down until it can be fixed? It would be fine if it didn&#039;t hang for 3 minutes, but using this with web applications those 3 minutes is unacceptable.

Am I doing it wrong?</description>
		<content:encoded><![CDATA[<p>I&#8217;m having an issue using this script. I have my setup as two mysqld servers with master-master replication. When I unplug the network cable to master1 the mysql-proxy takes 3 minutes to failover to master2 and only marks master1 into state=2 (down) for 4 seconds. Then it &#8216;wakes it up&#8217; again to state=0 (unknown). Upon the next query it takes another 3 minutes to fail (3 minutes because of the tcp timeout?) back to state=2 and then the whole cycle stars over again.</p>
<p>Why would it try to wake up the master1 after 4 seconds? What if the master1 machine goes down for the entire night, shouldn&#8217;t it just keep it down until it can be fixed? It would be fine if it didn&#8217;t hang for 3 minutes, but using this with web applications those 3 minutes is unacceptable.</p>
<p>Am I doing it wrong?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diego</title>
		<link>http://www.pythian.com/news/896/simple-mysql-proxy-failover/#comment-362941</link>
		<dc:creator>Diego</dc:creator>
		<pubDate>Tue, 16 Jun 2009 16:26:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/896/simple-mysql-proxy-failover#comment-362941</guid>
		<description>Hi Kyle,

This has been fixed on 0.7.0 (we have binaries available for 0.7.1 here http://dev.mysql.com/downloads/mysql-proxy/

Thanks</description>
		<content:encoded><![CDATA[<p>Hi Kyle,</p>
<p>This has been fixed on 0.7.0 (we have binaries available for 0.7.1 here <a href="http://dev.mysql.com/downloads/mysql-proxy/" rel="nofollow">http://dev.mysql.com/downloads/mysql-proxy/</a></p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle</title>
		<link>http://www.pythian.com/news/896/simple-mysql-proxy-failover/#comment-362937</link>
		<dc:creator>Kyle</dc:creator>
		<pubDate>Tue, 16 Jun 2009 15:04:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/896/simple-mysql-proxy-failover#comment-362937</guid>
		<description>We had the same issue with 0.6.1 and rolled back to 0.6.0.  0.6.1 basically broke load balancing.</description>
		<content:encoded><![CDATA[<p>We had the same issue with 0.6.1 and rolled back to 0.6.0.  0.6.1 basically broke load balancing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sheeri Cabral</title>
		<link>http://www.pythian.com/news/896/simple-mysql-proxy-failover/#comment-336480</link>
		<dc:creator>Sheeri Cabral</dc:creator>
		<pubDate>Tue, 03 Feb 2009 21:27:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/896/simple-mysql-proxy-failover#comment-336480</guid>
		<description>Erol,

Having the *exact* error would be useful.  However, try doing a 

telnet 192.168.100.21 3306 

from the proxy machine to see if you can connect to the backend.

Also, you are aware that the proxy sits on port 4040 by default, right?  So to connect you have to do:

mysql -h proxyserver -u user -p -P4040</description>
		<content:encoded><![CDATA[<p>Erol,</p>
<p>Having the *exact* error would be useful.  However, try doing a </p>
<p>telnet 192.168.100.21 3306 </p>
<p>from the proxy machine to see if you can connect to the backend.</p>
<p>Also, you are aware that the proxy sits on port 4040 by default, right?  So to connect you have to do:</p>
<p>mysql -h proxyserver -u user -p -P4040</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erol</title>
		<link>http://www.pythian.com/news/896/simple-mysql-proxy-failover/#comment-333565</link>
		<dc:creator>Erol</dc:creator>
		<pubDate>Mon, 26 Jan 2009 20:01:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/896/simple-mysql-proxy-failover#comment-333565</guid>
		<description>Thanks fr this snippet of code. 
One problem when I roll it out Im getting connection refused even though the proxy admin shows both backends

I start it with this:

/usr/local/sbin/mysql-proxy --proxy-lua-script=/opt/scripts/failover.lua --proxy-backend-addresses=192.168.100.21:3306 --proxy-backend-addresses=192.168.100.20:3306

The failover.lua is your code?
Any ideas what may cause this?</description>
		<content:encoded><![CDATA[<p>Thanks fr this snippet of code.<br />
One problem when I roll it out Im getting connection refused even though the proxy admin shows both backends</p>
<p>I start it with this:</p>
<p>/usr/local/sbin/mysql-proxy &#8211;proxy-lua-script=/opt/scripts/failover.lua &#8211;proxy-backend-addresses=192.168.100.21:3306 &#8211;proxy-backend-addresses=192.168.100.20:3306</p>
<p>The failover.lua is your code?<br />
Any ideas what may cause this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: YoungWoo Kim</title>
		<link>http://www.pythian.com/news/896/simple-mysql-proxy-failover/#comment-175104</link>
		<dc:creator>YoungWoo Kim</dc:creator>
		<pubDate>Tue, 01 Apr 2008 02:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/896/simple-mysql-proxy-failover#comment-175104</guid>
		<description>Sheeri,
Thanks for your advice.

So, I tested mysql-proxy 0.6.0.

As a result, It works fine with 0.6.0. :-)

In my case, I have two mysql servers with master-master replication scheme.

I think, mysql-proxy(0.6.1) does not recognize backends status(UP or DOWN).

Thanks.

Regards,
yw kim.</description>
		<content:encoded><![CDATA[<p>Sheeri,<br />
Thanks for your advice.</p>
<p>So, I tested mysql-proxy 0.6.0.</p>
<p>As a result, It works fine with 0.6.0. :-)</p>
<p>In my case, I have two mysql servers with master-master replication scheme.</p>
<p>I think, mysql-proxy(0.6.1) does not recognize backends status(UP or DOWN).</p>
<p>Thanks.</p>
<p>Regards,<br />
yw kim.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sheeri Cabral</title>
		<link>http://www.pythian.com/news/896/simple-mysql-proxy-failover/#comment-174972</link>
		<dc:creator>Sheeri Cabral</dc:creator>
		<pubDate>Mon, 31 Mar 2008 16:58:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/896/simple-mysql-proxy-failover#comment-174972</guid>
		<description>YoungWoo -- I&#039;m using 

mysql-proxy-0.6.0-solaris10-x86_64

Can you give more details on how it does not work?  ie, are you getting a syntax error with Lua, or are you finding that it does not work with failover?  If that&#039;s the case, what&#039;s the behavior you&#039;re seeing -- are you seeing it do round-robin load balancing?  Have you set up 2 backend servers with the --proxy-addresses startup option to mysql-proxy?</description>
		<content:encoded><![CDATA[<p>YoungWoo &#8212; I&#8217;m using </p>
<p>mysql-proxy-0.6.0-solaris10-x86_64</p>
<p>Can you give more details on how it does not work?  ie, are you getting a syntax error with Lua, or are you finding that it does not work with failover?  If that&#8217;s the case, what&#8217;s the behavior you&#8217;re seeing &#8212; are you seeing it do round-robin load balancing?  Have you set up 2 backend servers with the &#8211;proxy-addresses startup option to mysql-proxy?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: YoungWoo Kim</title>
		<link>http://www.pythian.com/news/896/simple-mysql-proxy-failover/#comment-174968</link>
		<dc:creator>YoungWoo Kim</dc:creator>
		<pubDate>Mon, 31 Mar 2008 16:18:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/896/simple-mysql-proxy-failover#comment-174968</guid>
		<description>Hi Sheeri .
Thanks for your posting.
I got a Problem. It does not work mysql-proxy 0.6.1 on RHEL4.
Which version of mysql-proxy do you use for testing your lua script?

Thanks.

yw kim.</description>
		<content:encoded><![CDATA[<p>Hi Sheeri .<br />
Thanks for your posting.<br />
I got a Problem. It does not work mysql-proxy 0.6.1 on RHEL4.<br />
Which version of mysql-proxy do you use for testing your lua script?</p>
<p>Thanks.</p>
<p>yw kim.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

