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 wrote: > > Hello. > I'm using MySQL-3.23.38 on 5 RedHat 7.1/7.2 servers composed by one master > and 4 mysql slave, every write is made on the master and then replicated to > the slave. > The problem is that if one client crash or must be rebooted i've to: > > - on the mysql master stop mysql, delete binlogfile, tar all the data in a > file and then restart mysql > - on ALL the mysql slave stop mysql, delete all data, get the tar file from > the master and the restart mysql > > so i've to restart all mysql slave even if only one is really "crash", if i > don't do this i loose the syncronization between master and slave (as shown > in the mysql.log). > As your experience what do you do when a mysql slave "crash" and loose the > sync? I would like to use a method to restart only the crashed client without > touch other's slave and without restart master. > > I could make a backup script that get all the data from the the master (like > mysqlhotcopy) without restart nothing, but what about the binlog file? i > could FLUSH them in the server but then other slave will loose the sync .... > I appreciate any help or suggestion. > > Best Regards. > -- > 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 --------------------------------------------------------------------- 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
