Actually if you google master master replication you should be able to
find a lot of tutorial like this one:
You also might want to search adding heartbeat so you can have an auto
fail over using a floating IP.
Hope this helps.
On Fri, Apr 6, 2012 at 9:02 AM, Kaushal Shriyan
> On Fri, Apr 6, 2012 at 6:11 AM, Rick James <rjames@stripped> wrote:
>> Slaves are useful for scaling reads.
>> Master-Master, with one of them writable, is the best config for quickly
>> failing over if one machine dies.
>> Any number of Slaves can be hung off them; it is best to split the slaves
>> Master-Relay-Slave -- the middle guy is a "single point of failure", hence
>> not advisable
>> Circular Replication (3+ machines replicating in one direction) is not
>> advised -- if one dies, you have a mess.
>> Writing to two masters (Dual or Circular) does not give you write scaling
>> -- all writes have to be performed by all servers. That is, you cannot
>> scale writes by any Replication configuration.
> Hi Rick
> Typically Master Master Replication is the preferred over the other
> replication methods ? Any documentation please. Master-Master, with one of
> them writable, not sure i understand that so write on one master and what
> about the other master.
>> On 4/5/12 5:15 PM, Kaushal Shriyan wrote:
>>> Any documentation regarding setting up MySQL Replication. I have been
>>> referring to
>>> also what are the typical scenarios to be setup viz Master Master Slave or
>>> Master Slave or Master Slave Slave. Help me understand the pros and cons
>>> this various combinations.
>>> Thanks and Regards,
>> Rick James - MySQL Geek
>> MySQL Replication Mailing List
>> For list archives:
>> To unsubscribe: