<?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: MySQL Master-Master replication manager released</title>
	<atom:link href="http://kovyrin.net/2007/04/05/mysql-master-master-replication-manager-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://kovyrin.net/2007/04/05/mysql-master-master-replication-manager-released/</link>
	<description>Yet Another Admin&#039;s blog</description>
	<lastBuildDate>Thu, 04 Feb 2010 07:58:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: PSI</title>
		<link>http://kovyrin.net/2007/04/05/mysql-master-master-replication-manager-released/comment-page-1/#comment-106752</link>
		<dc:creator>PSI</dc:creator>
		<pubDate>Mon, 15 Mar 2010 11:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kovyrin.net/2007/04/05/mysql-master-master-replication-manager-released/#comment-106752</guid>
		<description>For MySQL 5.0.2 or above

In the my.cnf file on server1 add:
auto_increment_increment=2
auto_increment_offset=1

In the my.cnf file on server2 add:
auto_increment_increment=2
auto_increment_offset=2

This will make the auto-increment on server1 go, 1,3,5,7,9,etc... and on server2 go, 2,4,6,8,etc... thereby preventing collisions.</description>
		<content:encoded><![CDATA[<p>For MySQL 5.0.2 or above</p>
<p>In the my.cnf file on server1 add:<br />
auto_increment_increment=2<br />
auto_increment_offset=1</p>
<p>In the my.cnf file on server2 add:<br />
auto_increment_increment=2<br />
auto_increment_offset=2</p>
<p>This will make the auto-increment on server1 go, 1,3,5,7,9,etc&#8230; and on server2 go, 2,4,6,8,etc&#8230; thereby preventing collisions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scoundrel</title>
		<link>http://kovyrin.net/2007/04/05/mysql-master-master-replication-manager-released/comment-page-1/#comment-86130</link>
		<dc:creator>Scoundrel</dc:creator>
		<pubDate>Mon, 15 Mar 2010 21:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kovyrin.net/2007/04/05/mysql-master-master-replication-manager-released/#comment-86130</guid>
		<description>2Patchlog: This software works with classic master-master schemes where one of the master is active (handles writes and, sometimes, reads) and other is passive (receives updates via replication and could handle reads).</description>
		<content:encoded><![CDATA[<p>2Patchlog: This software works with classic master-master schemes where one of the master is active (handles writes and, sometimes, reads) and other is passive (receives updates via replication and could handle reads).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PatchLog</title>
		<link>http://kovyrin.net/2007/04/05/mysql-master-master-replication-manager-released/comment-page-1/#comment-85641</link>
		<dc:creator>PatchLog</dc:creator>
		<pubDate>Mon, 15 Mar 2010 18:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kovyrin.net/2007/04/05/mysql-master-master-replication-manager-released/#comment-85641</guid>
		<description>is the web server able to write to any of the masters at any time ? what happens with databases that use auto increment fields ? how do you manage conflicts ?</description>
		<content:encoded><![CDATA[<p>is the web server able to write to any of the masters at any time ? what happens with databases that use auto increment fields ? how do you manage conflicts ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
