.
-Original Message-
From: Daevid Vincent [mailto:dae...@daevid.com]
Sent: Wednesday, May 20, 2009 4:49 PM
To: mysql@lists.mysql.com
Cc: 'Gavin Towey'; 'Claudio Nanni'
Subject: RE: mySQL slave IO Running and SQL Running
Well, in 90% of our cases it is. Most often caused by some dumb-ass
(usually
We have a master / slave setup and as you know, one bad query can ruin your
whole day. Or if you accidentally write to the slave when you meant to write
to the master, or any number of other things that break the fragility of a
replication setup.
The magic incantation to get them synched again
Yeah Daevid! I know very well the issue!
first set the slave to READ ONLY
[mysqld]
read-only
then there is a configuration option to tell the server to skip some type of
errors automatically
slave-skip-errors=
problems.
-Original Message-
From: Claudio Nanni [mailto:claudio.na...@gmail.com]
Sent: Wednesday, May 20, 2009 12:49 PM
To: Daevid Vincent
Cc: mysql@lists.mysql.com
Subject: Re: mySQL slave IO Running and SQL Running
Yeah Daevid! I know very well the issue!
first set the slave to READ
To: Claudio Nanni; Daevid Vincent
Cc: mysql@lists.mysql.com
Subject: RE: mySQL slave IO Running and SQL Running
Please note that this is *NOT* a way to get them synched again
In fact if you have to skip a replication statement on the
slave then it is usually a sign your slave has different
