<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/link/2974185">
<title>Public marks on http://www.howtoforge.com/setting-up-master-master-replication-on-four-nodes-with-mysql-5-on-debian-etch</title>
<description>Public marks on http://www.howtoforge.com/setting-up-master-master-replication-on-four-nodes-with-mysql-5-on-debian-etch</description>
<link>http://blogmarks.net/marks/link/2974185</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/camel/mark/1058065876"/>
<rdf:li resource="http://blogmarks.net/api/user/falko/mark/1058065735"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/camel/mark/1058065876">
<title>Setting Up Master-Master Replication On Four Nodes With MySQL 5 On Debian Etch | HowtoForge - Linux Howtos and Tutorials</title>
<link>http://www.howtoforge.com/setting-up-master-master-replication-on-four-nodes-with-mysql-5-on-debian-etch</link>
<description>This tutorial explains how you can set up MySQL master-master replication on four MySQL nodes (running on Debian Etch). The difference to a two node master-master replication (which is explained here) is that if you have more than two nodes, the replication goes in a circle, i.e., with four nodes, the replication goes from node1 to node2, from node2 to node3, from node3 to node4, and from node4 to node1.

Since version 5, MySQL comes with built-in support for master-master replication, solving the problem that can happen with self-generated keys. In former MySQL versions, the problem with master-master replication was that conflicts arose immediately if node A and node B both inserted an auto-incrementing key on the same table. The advantages of master-master replication over the traditional master-slave replication are that you don't have to modify your applications to make write accesses only to the master, and that it is easier to provide high-availability because if the master fails, you still have the other master. </description>
<dc:date>2008-11-20T16:02:23Z</dc:date>
<dc:author>camel</dc:author>
<dc:subject>linux, debian, mysql, tutorial, applications, replication</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.howtoforge.com/setting-up-master-master-replication-on-four-nodes-with-mysql-5-on-debian-etch"><img border="0" src="http://blogmarks.net/screenshots/2008/11/20/7b7ac19a04784ca73e3e65f56b332d07.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.howtoforge.com/setting-up-master-master-replication-on-four-nodes-with-mysql-5-on-debian-etch">Setting Up Master-Master Replication On Four Nodes With MySQL 5 On Debian Etch | HowtoForge - Linux Howtos and Tutorials</a></h4>
 
by <a href="http://blogmarks.net/user/camel">camel</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2974185">1 other(s)</a> 
<p class="description">This tutorial explains how you can set up MySQL master-master replication on four MySQL nodes (running on Debian Etch). The difference to a two node master-master replication (which is explained here) is that if you have more than two nodes, the replication goes in a circle, i.e., with four nodes, the replication goes from node1 to node2, from node2 to node3, from node3 to node4, and from node4 to node1.

Since version 5, MySQL comes with built-in support for master-master replication, solving the problem that can happen with self-generated keys. In former MySQL versions, the problem with master-master replication was that conflicts arose immediately if node A and node B both inserted an auto-incrementing key on the same table. The advantages of master-master replication over the traditional master-slave replication are that you don't have to modify your applications to make write accesses only to the master, and that it is easier to provide high-availability because if the master fails, you still have the other master. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/debian">debian</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mysql">mysql</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutorial">tutorial</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/applications">applications</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/replication">replication</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058065876">Copy</a> | 
<a href="http://blogmarks.net/link/2974185">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/falko/mark/1058065735">
<title>Setting Up Master-Master Replication On Four Nodes With MySQL 5 On Debian Etch | HowtoForge - Linux Howtos and Tutorials</title>
<link>http://www.howtoforge.com/setting-up-master-master-replication-on-four-nodes-with-mysql-5-on-debian-etch</link>
<description>This tutorial explains how you can set up MySQL master-master replication on four MySQL nodes (running on Debian Etch). The difference to a two node master-master replication is that if you have more than two nodes, the replication goes in a circle, i.e., with four nodes, the replication goes from node1 to node2, from node2 to node3, from node3 to node4, and from node4 to node1.</description>
<dc:date>2008-11-20T12:45:11Z</dc:date>
<dc:author>falko</dc:author>
<dc:subject>debian, master-master replication, replication, mysql</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.howtoforge.com/setting-up-master-master-replication-on-four-nodes-with-mysql-5-on-debian-etch"><img border="0" src="http://blogmarks.net/screenshots/2008/11/20/7b7ac19a04784ca73e3e65f56b332d07.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.howtoforge.com/setting-up-master-master-replication-on-four-nodes-with-mysql-5-on-debian-etch">Setting Up Master-Master Replication On Four Nodes With MySQL 5 On Debian Etch | HowtoForge - Linux Howtos and Tutorials</a></h4>
 
by <a href="http://blogmarks.net/user/falko">falko</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2974185">1 other(s)</a> 
<p class="description">This tutorial explains how you can set up MySQL master-master replication on four MySQL nodes (running on Debian Etch). The difference to a two node master-master replication is that if you have more than two nodes, the replication goes in a circle, i.e., with four nodes, the replication goes from node1 to node2, from node2 to node3, from node3 to node4, and from node4 to node1.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/debian">debian</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/master-master%2Breplication">master-master replication</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/replication">replication</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mysql">mysql</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058065735">Copy</a> | 
<a href="http://blogmarks.net/link/2974185">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>