Replication, log info

------=_NextPart_000_BAD2_01CBCDA2.0F7430A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

One more bit of information... this is from the error log:

110215 8:19:32 [ERROR] Error reading relay log event: slave SQL thread =
aborted because of I/O error
110215 8:19:32 [ERROR] Slave SQL: Relay log read failure: Could not =
parse relay log event entry. The possible r
easons are: the master's binary log is corrupted (you can check this by =
running 'mysqlbinlog' on the binary log)
, the slave's relay log is corrupted (you can check this by running =
'mysqlbinlog' on the relay log), a network p
roblem, or a bug in the master's or slave's MySQL code. If you want to =
check the master's binary log or slave's
relay log, you will be able to know their names by issuing 'SHOW SLAVE =
STATUS' on this slave. Error_code: 1594
110215 8:19:32 [ERROR] Error running query, slave SQL thread aborted. =
Fix the problem, and restart the slave SQ
L thread with "SLAVE START". We stopped at log 'mysql-bin.000717' =
position 552321409
110215 8:19:32 [Note] Slave I/O thread: connected to master =
'xxx@mysql3:3306',replication started in log 'm
ysql-bin.000717' at position 643066423
110215 8:19:33 [ERROR] Error reading packet from server: log event =
entry exceeded max_allowed_packet; Increase
max_allowed_packet on master ( server_errno=3D1236)
110215 8:19:33 [ERROR] Slave I/O: Got fatal error 1236 from master when =
reading data from binary log: 'log even
t entry exceeded max_allowed_packet; Increase max_allowed_packet on =
master', Error_code: 1236
110215 8:19:33 [Note] Slave I/O thread exiting, read up to log =
'mysql-bin.000717', position 643066423
110216 5:15:20 [Note] Slave SQL thread initialized, starting =
replication in log 'mysql-bin.000717' at position
552321409, relay log './mysqly_liv-relay.000127' position: 74666916
110216 5:15:20 [ERROR] Error in Log_event::read_log_event(): 'Sanity =
check failed', data_len: 40173568, event_t
ype: 87
110216 5:15:20 [ERROR] Error reading relay log event: slave SQL thread =
aborted because of I/O error
110216 5:15:20 [ERROR] Slave SQL: Relay log read failure: Could not =
parse relay log event entry. The possible r
easons are: the master's binary log is corrupted (you can check this by =
running 'mysqlbinlog' on the binary log)
, the slave's relay log is corrupted (you can check this by running =
'mysqlbinlog' on the relay log), a network p
roblem, or a bug in the master's or slave's MySQL code. If you want to =
check the master's binary log or slave's
relay log, you will be able to know their names by issuing 'SHOW SLAVE =
STATUS' on this slave. Error_code: 1594
110216 5:15:20 [ERROR] Error running query, slave SQL thread aborted. =
Fix the problem, and restart the slave SQ
L thread with "SLAVE START". We stopped at log 'mysql-bin.000717' =
position 552321409
110216 5:15:20 [Note] Slave I/O thread: connected to master =
'xxx@mysql3:3306',replication started in log 'm
ysql-bin.000717' at position 643066423
110216 5:15:20 [ERROR] Error reading packet from server: log event =
entry exceeded max_allowed_packet; Increase
max_allowed_packet on master ( server_errno=3D1236)
110216 5:15:20 [ERROR] Slave I/O: Got fatal error 1236 from master when =
reading data from binary log: 'log even
t entry exceeded max_allowed_packet; Increase max_allowed_packet on =
master', Error_code: 1236
110216 5:15:20 [Note] Slave I/O thread exiting, read up to log =
'mysql-bin.000717', position 643066423
~
Thanks,

Carl
------=_NextPart_000_BAD2_01CBCDA2.0F7430A0--

Re: Replication, log info

--000e0cd1fc6a7bd586049c64f3f6
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Feb 16, 2011 at 12:23 PM, Carl wrote:

> 110216 5:15:20 [ERROR] Error reading packet from server: log event entry
> exceeded max_allowed_packet; Increase
> max_allowed_packet on master ( server_errno=1236)
>

This seems to be the major player, here. I would make sure to increase the
setting identically on both sides, though.

I'm not entirely sure how this would happen - maybe due to making a
borderline-sized query deterministic?


--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

--000e0cd1fc6a7bd586049c64f3f6--

Re: Replication, log info

------=_NextPart_000_C622_01CBCDAC.F8A62C60
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It won't hurt anything to change the mac_allowed_packet size so I will =
increase it (it is set to 80MB, I will double it and see what happens it =
the future.)

Does anyone know if there are issues replicating blobs (I read yesterday =
that these sometimes cause problems)? I am just trying to see if I am =
setting myself up for future problems.

Thanks,

Carl
----- Original Message -----=20
From: Johan De Meersman=20
To: Carl=20
Cc: mysql@lists.mysql.com=20
Sent: Wednesday, February 16, 2011 6:55 AM
Subject: Re: Replication, log info




On Wed, Feb 16, 2011 at 12:23 PM, Carl wrote:

110216 5:15:20 [ERROR] Error reading packet from server: log event =
entry exceeded max_allowed_packet; Increase
max_allowed_packet on master ( server_errno=3D1236)

This seems to be the major player, here. I would make sure to increase =
the setting identically on both sides, though.

I'm not entirely sure how this would happen - maybe due to making a =
borderline-sized query deterministic?


--=20
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

------=_NextPart_000_C622_01CBCDAC.F8A62C60--