PUBLIC MARKS with tags mysql & replication

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.

Flipper is a tool for managing pairs of MySQL servers replicating to each other (commonly known as master-master replication or dual-master replication). Master-master replication is a great way of ensuring high availability for MySQL databases - it enables one half of the pair to be taken offline for maintenance work while the other half carries on dealing with queries from clients. Flipper achieves this by moving IP addresses based on a role ("read-only", "writable") between the two nodes in the master pair, to ensure that each role is available. Flipper is written in perl, and has been designed to be as portable as possible.

This short article explains how you can use a short script to check whether your MySQL master master replication is working as expected or not.

MySQL Replication Manager est une interface Web pour surveiller une architecture maître esclave. Elle permet simplement de lancer le maître et l'esclave, de gérer les logs et de surveiller l'état de fonctionnement. Il vous faut bien sûr les droits d'administration.

mysqlslavesync entre dans la famille des automatiseurs : tous ces outils qui permettent de mettre en place une solution standardisée. Ici, il s'agit de mettre en place la réplication MySQL sur un nouvel esclave. "L'outil se connecte au maître, effectue un dump ou un mysqlhotcopy, transfert les données, installe les données, puis configure les paramètres de réplication." Et voila, c'est tout. Si vous devez multiplier rapidement les esclaves, cela sera un répit important pour vos amis administrateur.

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.

Consider the following pseudo-code: $nid = node_save($data); $node = node_load($nid); Because node_save() executes a mutator query (an INSERT or UPDATE statement) is has to be executed on the master, so the master can propagate the changes to the slaves. Because node_load() uses a read-only query, it can go to the master or any of the available slaves. Because of the lack of synchronization between master and slaves, there is one obvious caveat: when we execute node_load() the slaves might not have been updated.

MMM (MySQL Master-Master Replication Manager) is set of flexible scripts to perform monitoring and management of MySQL Masrter-Master replication cluster configurations.

capttofu: MySQL Multi-Master Replication

This article explains how to avoid problems, help your slaves stay in sync with the master, and recover from disasters more quickly.

Ce tutorial décrit comment configurer une réplication MySQL de maître à maître. Nous devons assurer la réplication de serveur pour obtenir la haute disponibilité. Dans mon cas, j'ai besoin de deux maîtres pour qu'ils soient synchronisés l'un avec l'autre : si l'un deux tombe, l'autre prend la relève, et aucune donnée n'est perdu. De même, lorsque le deuxième serveur revient, il sera capable de rattrapper le survivant.

You may know about the MySQL Cluster, which is a complex architecture to achieve high availability and performance. One of the advantages of MySQL Cluster is that each node is a peer to the others, whereas in a normal replicating system you have a master

Replication FAQ. Q: How do I configure a slave if the master is running and I do not want to stop it? A: There are several possibilities. If you have taken a snapshot backup of the master at some point and recorded the binary log filename and offset (fr

There are only a few steps to setting up replication. The first step is to set up a user account to use only for replication. It's best not to use an existing account for security reasons. To do this, enter an SQL statement like the following on the maste

This tutorial describes how to set up database replication in MySQL. MySQL replication allows you to have an exact copy of a database from a master server on another server (slave), and all updates to the database on the master server are immediately repl

So what would be my list of limits and watch outs in this case ?