This way is very well, but it has to do lots of human work.
David Yeung, In China, Beijing.
My First Blog:http://yueliangdao0608.cublog.cn
My Second Blog:http://yueliangdao0608.blog.51cto.com
My Msn: yueliangdao0608@stripped
2010/11/24 Rolando Edwards <redwards@stripped>
> MySQL, by design, cannot do that.
> A DB Server can be Master to Multiple Slaves
> Think of the CHANGE MASTER TO command.
> Its internal design cannot accommodate reading from more than one set of
> relay logs.
> You could attempt something convoluted, like
> 1) STOP SLAVE;
> 2) CHANGE MASTER TO <Master 1>
> 3) START SLAVE;
> 4) Read and process some binary log transactions, wait till you are zero
> sec behind master
> 5) STOP SLAVE;
> 6) CHANGE MASTER TO <Master 2>
> 7) START SLAVE;
> 8) Read some process binary log transactions, wait till you are zero sec
> behind master
> 9) Repeat from step 1
> Make sure Each Master is updating only one specific set of databases,
> mutual exclusive from other Masters
> Make sure you properly record the log file and log position from each
> I would never try this under normal circumstances.
> I think this was described in the "High Performance MySQL" book
> Rolando A. Edwards
> MySQL DBA (CMDBA)
> 155 Avenue of the Americas, Fifth Floor
> New York, NY 10013
> 212-625-5307 (Work)
> 201-660-3221 (Cell)
> AIM & Skype : RolandoLogicWorx
> -----Original Message-----
> From: Machiel Richards [mailto:machielr@stripped]
> Sent: Wednesday, November 24, 2010 7:20 AM
> To: mysql mailing list
> Subject: Another replication question
> Hi All
> I am back once again with another replication question (maybe this
> can also be handled by MMM but not sure) this time for a different
> We are trying to find out how to setup 3 different masters to
> replicate to a single slave server (without the need to have 3 different
> instances running on the slave machine).
> Does anybody have any ideas?
> Any ideas will be greatly appreciated.