To answer the original poster of this thread, it would help if you could
post more details about what happened such as error messages and mysqld
versions. My hunch is that the binlog got corrupted and the slave choked
on it. Did you try issuing 'SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1' (omit
GLOBAL if
Jeff Smelser wrote:
On Friday 08 April 2005 10:38 am, Chris Scheller wrote:
i have replication going between 2 boxes. the master crashed a few days
ago, and this morning i noticed that the slaves slave thread errored
out. the binary log and offset had changed on the master and the slave
couldn't sy
eplication failure is easier.
David Norman
Wells Fargo Services
-Original Message-
From: Jeff Smelser [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 14, 2005 1:16 PM
To: mysql@lists.mysql.com
Subject: Re: slave out of sync
On Friday 08 April 2005 10:38 am, Chris Scheller wrote:
> i hav
On Friday 08 April 2005 10:38 am, Chris Scheller wrote:
> i have replication going between 2 boxes. the master crashed a few days
> ago, and this morning i noticed that the slaves slave thread errored
> out. the binary log and offset had changed on the master and the slave
> couldn't sync up. i got
Hello.
Replication shouldn't die if one of the participants goes offline.
But unclean shutdowns of the master may cause inconsistencies between the
content of tables and the binary log in master; this can be avoided by
using InnoDB tables and the --innodb-safe-binlog option on the master.
Gleb Paharenko wrote:
>
But if you had an updates and deletes after crashing the master
your task became difficult. But the easiest way, as for me,
>
> is to clear the slave and setup replication again. You may use
think this is what i am going to have to do as i found more errors this
morning wit
Hello.
I think that it is possible using mysqlbinlog with options
--stop-position and --start-position to get missed data.
But if you had an updates and deletes after crashing the master
your task became difficult. But the easiest way, as for me,
is to clear the slave and setup replication
i have replication going between 2 boxes. the master crashed a few days
ago, and this morning i noticed that the slaves slave thread errored
out. the binary log and offset had changed on the master and the slave
couldn't sync up. i got the slave up and running again by changing the
log file and
