That's not entirely true.
You can have two instances of mysql running on the slave, and dbA connects to
one instance, and dbB connects to the other.
Jeff, when you say, "different databases", do you mean that each master has a
single mysql instance, and if you typed on M1,
"show databases" you'd see (for example), "dbA"
and if you did the same on M2, you'd see, "dbB"?
If so, I wonder if there is another way to get around it:
- create a virtual IP address that represents both masters. Use that virtual master in the my.cnf on the slave; each master has to
have an identical replication account
- put dbA and dbB on the slave
- restrict replication from each master to their respective databases - "dbA" and "dbB" - ie don't replicate changes to the
"mysql" database.
The two masters appear as one (which overcomes the single-IP-address in the slave's my.cnf file), and each master has a different
database inside the mysql instance, they aren't stepping on each others toes.
Just my 2 cents.
David.
Greg Donald wrote:
On 3/1/06, Jeff <[EMAIL PROTECTED]> wrote:
Does anyone know if it's possible to replicate to a single slave from
different databases on different masters?
For instance:
M1:dbA M2:dbB
\ /
rep rep
\ /
Slave
http://dev.mysql.com/doc/refman/5.1/en/replication-features.html
<snip>MySQL only supports one master and many slaves.</snip>
--
Greg Donald
Zend Certified Engineer
MySQL Core Certification
http://destiney.com/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
