Hello.
> I already tried the option --slave-skip-errors, but i didn't work as
> expected.
> When this option is enabled, the slave didn't report the error
message, but
> the slave is stopped due the error.
May be server dies due an error message which was not included in the
slave-skip-e
19.46
A: mysql@lists.mysql.com
Oggetto: Re: how use sql_slave_skip_counter to restore slave replication
(still catching up, sorry about the old issues)
Don't know what version is being used here, but one thing you might
want to use, if you're just going to skip the errors anyway (hopefully
(still catching up, sorry about the old issues)
Don't know what version is being used here, but one thing you might
want to use, if you're just going to skip the errors anyway (hopefully
you understand WHY you're getting them), is to start replication with
the
--slave-skip-errors
option -- you c
Hello.
> One think it is astonished: I can agree that there should bu some
>conflict, but why i have remove the same row, with the same key value
>several times about 5-6 times ).Do you have some knowledge of problem
>like that ?
It is difficult to say something, because the whole picture
Oggetto: Re: how use sql_slave_skip_counter to restore slave replication
Hello. > but the problem is the same and the command 'show slave status'
report >a skip_counter filed equals 0.
> Where I am wrong , some can help me ? This variable is the number of
events from the master
other than what Gleb says,
you can avoid the error using 'insert ignore into' or better yet
'replace into'
for every insert statement
AESYS S.p.A. [Enzo Arlati] wrote:
I'm trying to use teh parameter sql_slave_skip_counter at run-time to
restore slave replication.
When a slave replication bro
Hello.
> but the problem is the same and the command 'show slave status' report
>a skip_counter filed equals 0.
> Where I am wrong , some can help me ?
This variable is the number of events from the master that a slave
server should skip. sql_slave_skip_counter decrements each time the
s
I'm trying to use teh parameter sql_slave_skip_counter at run-time to
restore slave replication.
When a slave replication broke due some errors in code, my be a duplicate
key, the only working way to restore the replica where to delete the
existing record which conflicts whith the ones inserted by
