Re: R: how use sql_slave_skip_counter to restore slave replication

[Gleb Paharenko]

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 of your
application isn't clear for me. Provide short description of
application's logic, include CREATE statements for your tables
and main queries. Make it in a compact form as much as possible.
I have a question: queries which causes 'duplicate key' errors should
fail on the master, and therefore they can't be replicated. Are you
directly update your slave? Or probably you have an old version 
which is buggy?


AESYS S.p.A. [Enzo Arlati] wrote:
> So it should be possible to automate a skip of errors setting by code , at
> run-time, sql_slave_skip_counter = 1, each time I check the slave status and
> I found an error, and then I restart the slave
> Thanks, I should try this way.
> 
> One think it is astonished: I can agree that there should bu some conflict,
> but why i have remove the same row, with tha same key value several times
>  about 5-6 times ).
> Do you have some knowledge of problem like that ?


-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   Gleb.Paharenko@stripped
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
       <___/   www.mysql.com