You are right, but my master generate about 150Mb of binlog x day, i a slave fail after 4 day it will reexec a lot of query and take some time. how can i safely rotate the log in master+slaves without restarting them? The Mysql manual explain how to rotate from a `hostnmae`-bin`.002 (or > 001) file, but what about if the binlog is always the same? I could do a FLUSH MASTER in the master and then FLUSH SLAVE in the slaves, it wouldn't loose the sync?
Regards > When a slave crashes or reboots, it should start replicating from where it > left off--at least ours do work that way. The current replication state > is saved in master.info on the slave and when it starts up again, it > should read that file and resume reading the binlog on the master where it > left off. The master.info file contains the binlog#, location, user, > password, etc... neccessary to restart replication. > > In you case, does the slave give you any error messages in it's error log > about why it couldn't resume replication? If it doesn't try to start > replication, have you tried doing a 'slave start' on the slave after it > reboots? > > -Marc -- Davide Giunchi. Membro del FoLUG (Forlí Linux User Group) - http://folug.linux.it GPG Key available on http://www.keyserver.net Fingerprint: 8075 363A B4FA 0196 FEEC AF9C 19A9 66C7 CDAB D0D5 --------------------------------------------------------------------- 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
