MySQL Bugs: #31779: Repeatable crashes if replace original binary log with one created by 3.23 serve

Bug #31779	Repeatable crashes if replace original binary log with one created by 3.23 serve
Submitted:	23 Oct 2007 10:00	Modified:	1 Feb 2008 23:19
Reporter:	Sveta Smirnova	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S2 (Serious)
Version:	5.1 BK	OS:	Any
Assigned to:	Zhenxing He	CPU Architecture:	Any
Description:
If one replaced just created 4.1 binary log with one created by 3.23.58 server and then tried to replicate its content to the slave (ie by running CHANGE MASTER ...; START SLAVE command) both master and slave will crush repeatedly.

How to repeat:
See description.

Binary log is http://bugs.mysql.com/file.php?id=7608 (see also bug #31778).

Part of slave error log:

 Version: '5.1.23-beta-debug-log'  socket: '/tmp/mysql512.sock'  port: 33512  Source distribution
071023 10:01:04 [Note] Slave SQL thread initialized, starting replication in log 'mysqld511-apple-bin.000001' at position 73, relay log '/Users/apple/Appli  cations/mysql-5.1/data512/mysqld512-apple-relay-bin.000002' position: 159
071023 10:01:04 [ERROR] /Users/apple/Applications/mysql-5.1/libexec/mysqld: Out of memory at line 201, 'my_alloc.c'
071023 10:01:04 [ERROR] /Users/apple/Applications/mysql-5.1/libexec/mysqld: needed 4294967248 byte (0k), memory in use: 8909570 bytes (8701k)
071023 10:01:04 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysql  d to use more memory or you can add more swap space
071023 10:01:04 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Error_code: 1594
071023 10:01:04 [Note] Slave I/O thread exiting, read up to log 'mysqld511-apple-bin.000001', position 73
071023 10:01:16 - mysqld got signal 10;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=8388572
read_buffer_size=131072
max_used_connections=1
max_threads=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337617 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

071023 10:01:16 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts asa master and has his hostname changed!! Please use '--log-bin=/Users/apple/Applications/mysql-5.1/data512/mysqld512-apple-bin' to avoid this problem.
071023 10:01:16  InnoDB: Started; log sequence number 0 56221
071023 10:01:16 [Note] Recovering after a crash using /Users/apple/Applications/mysql-5.1/data512/mysqld512-apple-bin
071023 10:01:16 [Note] Starting crash recovery...
071023 10:01:16 [Note] Crash recovery finished.

Part of master error log:

 071023 11:25:30 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts asa master and has his hostname changed!! Please use '--log-bin=/Users/apple/Applications/mysql-5.1/data511/mysqld511-apple-bin' to avoid this problem.
071023 11:25:30  InnoDB: Started; log sequence number 0 60301
071023 11:25:30 [Note] Recovering after a crash using /Users/apple/Applications/mysql-5.1/data511/mysqld511-apple-bin
071023 11:25:30 [Note] Starting crash recovery...
071023 11:25:30 [Note] Crash recovery finished.
071023 11:25:31 [Note] Event Scheduler: Loaded 1 event
071023 11:25:31 [Note] /Users/apple/Applications/mysql-5.1/libexec/mysqld: ready for connections.
Version: '5.1.23-beta-debug-log'  socket: '/tmp/mysql511.sock'  port: 33511  Source distribution
Error: Packets out of order (Found: 0, expected 7)
net_serv.cc:914: failed assertion `0'
071023 11:25:44 - mysqld got signal 6;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=8388572
read_buffer_size=131072
max_used_connections=1
max_threads=151
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337617 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.