SEO

Hi,

I have experienced similar problems to the one you have; the problem you have is that the time gap between the failure and now is so big that you cannot resume replication, because of the big data portion you have to replicate.

When this happens to me, increasing the value of the variable you have posted did not work; i did:

1º Stop replication
2º Use mysqlbinlog to see what is on the repl files.
3º Manually apply the changes (on the slave, of course) to a defined position (50K queries far away the failure).
4º Start replication on this position, manually especifying the position on the command "start slave" (see manual).

This worked fine to me.

Regards.

-----Mensaje original-----
De: Dominik Klein [mailto:dk@in-telegence.net]
Enviado el: lunes 28 de abril de 2008 16:28
Para: mysql@lists.mysql.com
Asunto: Re: Error reading packet from server: Out of memory (Needed 6560 bytes) ( server_errno=5)


Hi.

Juan Eduardo Moreno wrote:
> Sorry, what is your setting for max_allowed_packet variable?

mysql> show variables like "%allowed%";
+--------------------+----------+
| Variable_name | Value |
+--------------------+----------+
| max_allowed_packet | 16776192 |
+--------------------+----------+
1 row in set (0.00 sec)

Here's an excerpt from the logs. It does not look like that value is
involved in this:

080428 13:07:04 [ERROR] Error reading packet from server: Out of memory
(Needed 2704 bytes) ( server_errno=5)
080428 13:07:04 [Note] Slave I/O thread: Failed reading log event,
reconnecting to retry, log 'SRV02bin.000131' position 447892967 080428 13:07:04 [Note] Slave: connected to master
'mmrepli@10.250.250.32:3306',replication resumed in log
'SRV02-bin.000131' at position 447892967
080428 13:22:14 [ERROR] Error reading packet from server: Out of memory
(Needed 2704 bytes) ( server_errno=5)
080428 13:22:14 [Note] Slave I/O thread: Failed reading log event,
reconnecting to retry, log 'SRV02-bin.000131' position 471157588 080428 13:22:14 [Note] Slave: connected to master
'mmrepli@10.250.250.32:3306',replication resumed in log
'SRV02-bin.000131' at position 471157588
080428 14:38:06 [ERROR] Error reading packet from server: Out of memory
(Needed 3464 bytes) ( server_errno=5)
080428 14:38:06 [Note] Slave I/O thread: Failed reading log event,
reconnecting to retry, log 'SRV02-bin.000131' position 583864714 080428 14:38:06 [Note] Slave: connected to master
'mmrepli@10.250.250.32:3306',replication resumed in log
'SRV02-bin.000131' at position 583864714
080428 15:13:24 [ERROR] Error reading packet from server: Out of memory
(Needed 3128 bytes) ( server_errno=5)
080428 15:13:24 [Note] Slave I/O thread: Failed reading log event,
reconnecting to retry, log 'SRV02-bin.000131' position 635409380 080428 15:13:24 [Note] Slave: connected to master
'mmrepli@10.250.250.32:3306',replication resumed in log
'SRV02-bin.000131' at position 635409380
080428 15:32:14 [ERROR] Error reading packet from server: Out of memory
(Needed 2688 bytes) ( server_errno=5)
080428 15:32:14 [Note] Slave I/O thread: Failed reading log event,
reconnecting to retry, log 'SRV02-bin.000131' position 665146758 080428 15:32:14 [Note] Slave: connected to master
'mmrepli@10.250.250.32:3306',replication resumed in log
'SRV02-bin.000131' at position 665146758

Regards
Dominik

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=f...as@jazztel.com


Antes de imprimir este e-mail piense bien si es necesario hacerlo.

Antes de imprimir este e-mail piense bien si es necesario hacerlo.

*********
Este mensaje es privado y CONFIDENCIAL y se dirige exclusivamente a su destinatario. Si usted ha recibido este mensaje por error, no debe revelar, copiar, distribuir o usarlo en ningún sentido. Le rogamos lo comunique al remitente y borre dicho mensaje y cualquier documento adjunto que pudiera contener. El correo electrónico via Internet no permite asegurar la confidencialidad de los mensajes que se transmiten ni su integridad o correcta recepción. JAZZTEL no asume responsabilidad por estas circunstancias. Si el destinatario de este mensaje no consintiera la utilización del correo electrónico via Internet y la grabación de los mensajes, rogamos lo ponga en nuestro conocimiento de forma inmediata.Cualquier opinión expresada en este mensaje pertenece únicamente al autor remitente, y no representa necesariamente la opinión de JAZZTEL, a no ser que expresamente se diga y el remitente esté autorizado para hacerlo.
*********
This message is private and CONFIDENTIAL and it is intended exclusively for its addressee. If you receive this message in error, you should not disclose, copy, distribute this e-mail or use it in any other way. Please inform the sender and delete the message and attachments from your system.Internet e-mail neither guarantees the confidentiality nor the integrity or proper receipt of the messages sent. JAZZTEL does not assume any liability for those circumstances. If the addressee of this message does not consent to the use of Internet e-mail and message recording, please notify us immediately.Any views or opinions contained in this message are solely those of the author, and do not necessarily represent those of JAZZTEL, unless otherwise specifically stated and the sender is authorised to do so.
*********

Francisco Rodrigo Cortinas Maseda wrote:
> Hi,
>
> I have experienced similar problems to the one you have; the problem you have is that the time gap between the failure and now is so big that you cannot resume replication, because of the big data portion you have to replicate.

Well, that was yesterday - so I guess I could.

I see the binlog ids where replication stopped and resumed. They match
every time. How would I find out that replication resumed at a wrong
position?

Regards
Dominik