ore than once.
>-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 9
y [mailto:gto...@ffn.com]
> Sent: Wednesday, May 20, 2009 1:20 PM
> 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
re just masking
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 th
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=
http://dev.mysql.com/doc/refman/5.1/en/replication-options-slave.html#option_mysqld
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 se
