MySQL Bothway Replication - Fail Back - Hold Master while Slave is Synchronizing.
MySQL Bothway Replication - Fail Back - Hold Master while Slave is Synchronizing. I have the following question: Is it possible to have a slave on machine M1 synchronizing with a master on another machine M2 while the master on the first machine M1 does not accept requests yet (i.e. it is not available to a client yet)? Background info: Why do I want this? Well, I have a configuration where two machines run MySQL. They are configured to replicate each others updates. Although two masters are effectively running, only one is used at a time. This is taken care of by the client. When the first machine fails, the client detects this and goes to the other machine. So for so good. When machine M1 comes on-line again then our client immediately starts to use it (fail-back) (it has - let's say - a preferred machine and I can't disable this). The database, however, is not correct yet. The slave needs to synchronize with M2 still. So we read old data. This situation could be avoided if we can let the master on M1 wait until the salve on M1 has completed its synchronization, and the databases are in sync again. Thanks, Johan. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Replication does not continue after removal/replace of network cable.
Jean-Luc Fontaine wrote: On Thursday 22 March 2001 16:46, Johan Vanroose wrote: From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Replication does not continue after removal/replace of network cable. Description: Configuration. Two servers (PCs) running mysql, both are master and slave to each other. Replication using binary log. Updates done (from the mysql console) on either server are replicated to the other. (The application (I) takes care that the updates are not conflicting.) So far so good. Now the problem. I remove a network cable from one of the servers. I do an update (insert into table) on server 1. I do a second update (again insert) on server 2. Of course the updates aren't replicated (no communication possible). However... when I replace the cable, the replication is not done for the previous two inserts. I waited 4 minutes... Still no replication. Hmmm. The same thing happened to me with the 3.23.35 rpm on Linux Redaht 7.0. I had to do a 'slave stop/start' for the slave to recover. Did you get any further with this problem? I tried MySQL support. But since we have no support contract I did not get anything usefull back (yet). They say it's an NT problem but your situation seems to prove different. Also the whole system runs happy - even MySQL (without its replication). Since all looks OK (i.e. the log files and master/slave status) I assume that MySQL just *forgets* to replicate. Kind regards, Johan. -- Jean-Luc Fontaine - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Test - Ignore.
Test, Please ignore. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
