MySQL Bugs: #35629: Replication stop: string "HY000Failed on my

Bug #35629	Replication stop: string "HY000Failed on my_ne" in relaylog
Submitted:	28 Mar 2008 1:58	Modified:	7 Oct 2008 12:42
Reporter:	Den Ivanov	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S1 (Critical)
Version:	5.0.52-enterprise-gpl-log	OS:	Solaris
Assigned to:		CPU Architecture:	Any

Description:
One of three slaves stoped today with message:
080328  1:04:24 [ERROR] Error in Log_event::read_log_event(): 'Event too big', data_len: 1177563184, event_type: 81
080328  1:04:24 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error
080328  1:04:24 [ERROR] Slave: Could not parse relay log event entry. The possible reasons 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 problem, 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: 0
080328  1:04:24 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.002468' position 315
.........................
Mysqlbinlog say:
# mysqlbinlog /var/log/mysql/db4-relay-bin.002337 >/dev/null
ERROR: Error in Log_event::read_log_event(): 'Event too big', data_len: 1177563184, event_type: 81

Could not read entry at offset 172988:Error in log format or read error
.........................
I found string "HY000Failed on my_ne" in relaylog near offset 172988.

How to repeat:
Read relaylog.

Thank you for the report.

Please provide output of select @@max_allowed_packet; on both master and slave.

Also please consider to upgrade to current version 5.0.58 and inform us if problem still exists. It contains fix for bug #26489 which can affect you.

max_allowed_packet same on both master and slaves:
At master: 16776192
At slaves: 16776192

I can't update to 5.0.58 now - my enterprise subscription period ended.

This is not a bug. The data you will store in the field needs more then 2^30 bytes  and your max_allowed_paket is set to just round about 2^24 bytes.

Look here for get more informations about data type limits:
http://dev.mysql.com/doc/refman/5.0/en/storage-requirements.html

Please alter your column to LONGBLOB or LONGTEXT because that are the only data types that are able to more until 2^32 bytes.

Also configure max_allowed_packet to a hire value.

>The data you will store in the field needs more then 2^30 bytes  and your
>max_allowed_paket is set to just round about 2^24 bytes.
You speak about what field? We do not use such long fields.
And why this data sucessfully replicated on other slaves?

Here are the informations we got from you:

"ERROR: Error in Log_event::read_log_event(): 'Event too big', data_len: 1177563184,
event_type: 81"

1177563184 is round about 2^30 byte

"max_allowed_packet same on both master and slaves:
At master: 16776192
At slaves: 16776192"

16776192 is just round about 2^24 byte

this means your packet size is too small.

relay log is obviously corrupted.
So far looks like a bug.

Sorry, this was my mistake.

For analyzing this we need to know exactly what you did. You told us that you use more then one slave and that it only fails on one slave. It would be nice to have a compare between failing and non failing so we need a diff of the logs or the log from the failing and from the working slave.

Also MySQL 5.0.52 is quite old. Please try one of our newer versions. At the moment the newest version is MySQL 5.0.58.

Unfortunately, these logs were not kept.

This seems to be a duplicate of bug #26489.

Please upgrade to MySQL 5.1 (actual version MySQL 5.1.28-rc). Feel free to re-open this bug report if you still have problems but I think the fix for the other bug report will fix this problem here too.