Problems with slave_skip_errors on replication

am 25.01.2010 13:36:47 von Wagner Bianchi

--0016e6d7e681364bf1047dfc6ca9
Content-Type: text/plain; charset=ISO-8859-1

Hi friends,

Last weekend I made an environment that use a MySQL Server version 4.1 that
was defined to be the MASTER and other one version 5.1 defined as SLAVE.

Because the application that was concept working over exception, often the
SLAVE server got new error and replication stops.

Well, I configured the my.cnf file of the SLAVE to slave_skip_errors as you
may see specified after this massage, but, the replication continue stops,
even after this configurations.

mysql> show variables like 'slave_skip_errors';
+-------------------+-------+
| Variable_name | Value |
+-------------------+-------+
| slave_skip_errors | 1 |
+-------------------+-------+
1 row in set (0.00 sec)
mysql> show slave status\G
*************************** 1. row ***************************
Slave_IO_State: Queueing master event to the relay log
Master_Host: 172.28.8.70
Master_User: slave
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: bmg58-bin.000265
Read_Master_Log_Pos: 251871
Relay_Log_File: pid-file-relay-bin.000007
Relay_Log_Pos: 961348
Relay_Master_Log_File: bmg58-bin.000003
Slave_IO_Running: Yes
Slave_SQL_Running: No
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 1062
Last_Error: Error 'Duplicate entry '731493' for key
'PRIMARY'' on query. Default database: 'database'. Query: 'INSERT
INTO tb_usuario (ocu_codigo, ocu_tipo, usu_codigo,
ocu_data, ocu_obs, login_responsavel, ocu_ip)
VALUES( null, 67,
'C986CC89AC1C071835E341D18011D25Z', now(),
'x.', 'x.sp', null )'
Skip_Counter: 0
Exec_Master_Log_Pos: 952913
Relay_Log_Space: 264590369
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 1062
Last_SQL_Error: Error 'Duplicate entry '731493' for key
'PRIMARY'' on query. Default database: 'database'. Query: 'INSERT
INTO tb_usuario (ocu_codigo, ocu_tipo, usu_codigo,
ocu_data, ocu_obs, login_responsavel, ocu_ip)
VALUES( null, 67,
'C986CC89AC1C071835E341D18011D25Z', now(),
'x', 'x.sp', null )'
1 row in set (0.00 sec)

Have other thing to do, or this problem is made by the mix of versions?

Best regards!
--
Wagner Bianchi - Web System Developer and Database Administrator
Phone: (31) 8654-9510 / 3272-0226
E-mail: wagnerbianchijr@gmail.com
Lattes: http://lattes.cnpq.br/2041067758113940
Twitter: http://twitter.com/wagnerbianchi
Skype: infodbacet

--0016e6d7e681364bf1047dfc6ca9--

Re: Problems with slave_skip_errors on replication

am 25.01.2010 13:47:19 von sureshkumarilu

--00504502c078de4bfe047dfc91bb
Content-Type: text/plain; charset=ISO-8859-1

Hi Wagner,

You have to start the server with the option as below for skipping the
error.

--slave-skip-errorr= 1062 or all

1062 - will skip the your error as the error number is 1062 and all will
skip all the errors.

You have to mention specific error numbers to skip the same.

--
Thanks
Suresh Kuna
MySQL DBA

On Mon, Jan 25, 2010 at 6:06 PM, Wagner Bianchi
wrote:

> Hi friends,
>
> Last weekend I made an environment that use a MySQL Server version 4.1 that
> was defined to be the MASTER and other one version 5.1 defined as SLAVE.
>
> Because the application that was concept working over exception, often the
> SLAVE server got new error and replication stops.
>
> Well, I configured the my.cnf file of the SLAVE to slave_skip_errors as you
> may see specified after this massage, but, the replication continue stops,
> even after this configurations.
>
> mysql> show variables like 'slave_skip_errors';
> +-------------------+-------+
> | Variable_name | Value |
> +-------------------+-------+
> | slave_skip_errors | 1 |
> +-------------------+-------+
> 1 row in set (0.00 sec)
> mysql> show slave status\G
> *************************** 1. row ***************************
> Slave_IO_State: Queueing master event to the relay log
> Master_Host: 172.28.8.70
> Master_User: slave
> Master_Port: 3306
> Connect_Retry: 60
> Master_Log_File: bmg58-bin.000265
> Read_Master_Log_Pos: 251871
> Relay_Log_File: pid-file-relay-bin.000007
> Relay_Log_Pos: 961348
> Relay_Master_Log_File: bmg58-bin.000003
> Slave_IO_Running: Yes
> Slave_SQL_Running: No
> Replicate_Do_DB:
> Replicate_Ignore_DB:
> Replicate_Do_Table:
> Replicate_Ignore_Table:
> Replicate_Wild_Do_Table:
> Replicate_Wild_Ignore_Table:
> Last_Errno: 1062
> Last_Error: Error 'Duplicate entry '731493' for key
> 'PRIMARY'' on query. Default database: 'database'. Query: 'INSERT
> INTO tb_usuario (ocu_codigo, ocu_tipo, usu_codigo,
> ocu_data, ocu_obs, login_responsavel, ocu_ip)
> VALUES( null, 67,
> 'C986CC89AC1C071835E341D18011D25Z', now(),
> 'x.', 'x.sp', null )'
> Skip_Counter: 0
> Exec_Master_Log_Pos: 952913
> Relay_Log_Space: 264590369
> Until_Condition: None
> Until_Log_File:
> Until_Log_Pos: 0
> Master_SSL_Allowed: No
> Master_SSL_CA_File:
> Master_SSL_CA_Path:
> Master_SSL_Cert:
> Master_SSL_Cipher:
> Master_SSL_Key:
> Seconds_Behind_Master: NULL
> Master_SSL_Verify_Server_Cert: No
> Last_IO_Errno: 0
> Last_IO_Error:
> Last_SQL_Errno: 1062
> Last_SQL_Error: Error 'Duplicate entry '731493' for key
> 'PRIMARY'' on query. Default database: 'database'. Query: 'INSERT
> INTO tb_usuario (ocu_codigo, ocu_tipo, usu_codigo,
> ocu_data, ocu_obs, login_responsavel, ocu_ip)
> VALUES( null, 67,
> 'C986CC89AC1C071835E341D18011D25Z', now(),
> 'x', 'x.sp', null )'
> 1 row in set (0.00 sec)
>
> Have other thing to do, or this problem is made by the mix of versions?
>
> Best regards!
> --
> Wagner Bianchi - Web System Developer and Database Administrator
> Phone: (31) 8654-9510 / 3272-0226
> E-mail: wagnerbianchijr@gmail.com
> Lattes: http://lattes.cnpq.br/2041067758113940
> Twitter: http://twitter.com/wagnerbianchi
> Skype: infodbacet
>

--00504502c078de4bfe047dfc91bb--

Re: Problems with slave_skip_errors on replication

am 25.01.2010 13:51:22 von Wagner Bianchi

--0016e6dab0345bbe6d047dfca08e
Content-Type: text/plain; charset=ISO-8859-1

Ok, Suresh. . .I started MySQL with slave_skip_errors = all and It solve the
problem!

Thanks.
WB
2010/1/25 Suresh Kuna

> Hi Wagner,
>
> You have to start the server with the option as below for skipping the
> error.
>
> --slave-skip-errorr= 1062 or all
>
> 1062 - will skip the your error as the error number is 1062 and all will
> skip all the errors.
>
> You have to mention specific error numbers to skip the same.
>
>
> --
> Thanks
> Suresh Kuna
> MySQL DBA
>
>
>
> On Mon, Jan 25, 2010 at 6:06 PM, Wagner Bianchi > > wrote:
>
>> Hi friends,
>>
>> Last weekend I made an environment that use a MySQL Server version 4.1
>> that
>> was defined to be the MASTER and other one version 5.1 defined as SLAVE.
>>
>> Because the application that was concept working over exception, often the
>> SLAVE server got new error and replication stops.
>>
>> Well, I configured the my.cnf file of the SLAVE to slave_skip_errors as
>> you
>> may see specified after this massage, but, the replication continue stops,
>> even after this configurations.
>>
>> mysql> show variables like 'slave_skip_errors';
>> +-------------------+-------+
>> | Variable_name | Value |
>> +-------------------+-------+
>> | slave_skip_errors | 1 |
>> +-------------------+-------+
>> 1 row in set (0.00 sec)
>> mysql> show slave status\G
>> *************************** 1. row ***************************
>> Slave_IO_State: Queueing master event to the relay log
>> Master_Host: 172.28.8.70
>> Master_User: slave
>> Master_Port: 3306
>> Connect_Retry: 60
>> Master_Log_File: X58-bin.000265
>> Read_Master_Log_Pos: 251871
>> Relay_Log_File: pid-file-relay-bin.000007
>> Relay_Log_Pos: 961348
>> Relay_Master_Log_File: X58-bin.000003
>> Slave_IO_Running: Yes
>> Slave_SQL_Running: No
>> Replicate_Do_DB:
>> Replicate_Ignore_DB:
>> Replicate_Do_Table:
>> Replicate_Ignore_Table:
>> Replicate_Wild_Do_Table:
>> Replicate_Wild_Ignore_Table:
>> Last_Errno: 1062
>> Last_Error: Error 'Duplicate entry '731493' for key
>> 'PRIMARY'' on query. Default database: 'database'. Query: 'INSERT
>> INTO tb_usuario (ocu_codigo, ocu_tipo, usu_codigo,
>> ocu_data, ocu_obs, login_responsavel, ocu_ip)
>> VALUES( null, 67,
>> 'C986CC89AC1C071835E341D18011D25Z', now(),
>> 'x.', 'x.sp', null )'
>> Skip_Counter: 0
>> Exec_Master_Log_Pos: 952913
>> Relay_Log_Space: 264590369
>> Until_Condition: None
>> Until_Log_File:
>> Until_Log_Pos: 0
>> Master_SSL_Allowed: No
>> Master_SSL_CA_File:
>> Master_SSL_CA_Path:
>> Master_SSL_Cert:
>> Master_SSL_Cipher:
>> Master_SSL_Key:
>> Seconds_Behind_Master: NULL
>> Master_SSL_Verify_Server_Cert: No
>> Last_IO_Errno: 0
>> Last_IO_Error:
>> Last_SQL_Errno: 1062
>> Last_SQL_Error: Error 'Duplicate entry '731493' for key
>> 'PRIMARY'' on query. Default database: 'database'. Query: 'INSERT
>> INTO tb_usuario (ocu_codigo, ocu_tipo, usu_codigo,
>> ocu_data, ocu_obs, login_responsavel, ocu_ip)
>> VALUES( null, 67,
>> 'C986CC89AC1C071835E341D18011D25Z', now(),
>> 'x', 'x.sp', null )'
>> 1 row in set (0.00 sec)
>>
>> Have other thing to do, or this problem is made by the mix of versions?
>>
>> Best regards!
>>
>

--0016e6dab0345bbe6d047dfca08e--