MaFai [EMAIL PROTECTED] wrote:
I would also like to know the impact when:-
- the master db fail
- a lot of insert/update transactions in the master, would it replicate
immediately to the 2nd database
If the mater db fail, how can be many inserts/updates?
- when the secondary db fail, the master cannot send the data to the 2nd,
would the data queue up ?
Master doesn't send data to the slave, it writes all successful transaction to the
binary logs. Slave connects to the master and read binary logs. So, if slave stops, it
will read logs from the position on with it stops.
- Any chance for the data in 2 db not sync, if so how to re-synchronize them
?
In some cases queries are not written to the binary logs or they are not replicated.
For example, if you specify binlog-do-db=some_db option on the master, current
database isn't 'some_db' and you execute query like 'INSERT INTO some_db.some_tbl ..'.
This query will not be written to the binary log.
All theses cases are described in the manual.
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ /Victoria Reznichenko
/ /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net
___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
