Bug #329 'Event too big' when using a small max_binlog_size

• Submitted: 26 Apr 2003 6:35
• Modified: 26 Apr 2003 6:36
• Reporter: Guilhem Bichot
• Status: Closed
• Category: MySQL Server: Replication
• Severity: S3 (Non-critical)
• Version: 4.0
• OS: Any (all)
• CPU Architecture: Any

[26 Apr 2003 6:35] Guilhem Bichot

Description:
With max_binlog_size=2M.

This is a random bug. One can also see
http://lists.mysql.com/list.php?1:mss:126046:ehnfndibmippkppmdmha
and SW 1328.

heikki@hundin:~/mysql-4.0/sql>
mysqld --defaults-file=/home/heikki/slavemy.cnf
021204 23:55:45  InnoDB: Started
mysqld: ready for connections
021204 23:55:45  Slave I/O thread: connected to master
'slaveuser@hundin:3307',
 replication started in log 'FIRST' at position 4
021204 23:57:42  Error in Log_event::read_log_event(): 'Event too big',
data_len
=1447971143,event_type=115
021204 23:58:03  Slave SQL thread: I/O error reading event(errno: -1
cur_log->e
rror: 12)
021204 23:58:03  Error reading relay log event: Aborting slave SQL thread
becaus
e of partial event read
021204 23:58:03  Could not parse log event entry, check the master for
binlog co
rruption
This may also be a network problem, or just a bug in the master or slave
code.
021204 23:58:03  Error running query, slave SQL thread aborted. Fix the
problem,
 and restart the slave SQL thread with "SLAVE START". We stopped at log
'binlog.
002' position 13659061

How to repeat:

[26 Apr 2003 6:36] Guilhem Bichot

Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 
http://www.mysql.com/downloads/

Fixed in 4.0.6