mariadb/mysql-test/suite/rpl
Manish Kumar 9aa79dc596 BUG#12400221 - 60926: BINARY LOG EVENTS LARGER THAN MAX_ALLOWED_PACKET
Problem
========
            
SQL statements close to the size of max_allowed_packet produce binary
log events larger than max_allowed_packet.
              
The reason why this failure is occuring is because the event length is
more than the total size of the max_allowed_packet + max_event_header
length. Now since the event length exceeds this size master Dump
thread is unable to send the packet on to the slave.
                      
That can happen e.g with row-based replication in Update_rows event.
            
Fix
====
          
The problem was fixed by increasing the max_allowed_packet for the
slave's threads (IO/SQL) by increasing it to 1GB.
This is done using the new server option included which is used to
regulate the max_allowed_packet of the slave thread (IO/SQL).
This causes the large packets to be received by the slave and apply
it successfully.
2012-05-21 12:57:39 +05:30
..
include BUG#49978: Replication tests don't clean up replication state at the end 2010-12-19 18:07:28 +01:00
r BUG#12400221 - 60926: BINARY LOG EVENTS LARGER THAN MAX_ALLOWED_PACKET 2012-05-21 12:57:39 +05:30
t BUG#12400221 - 60926: BINARY LOG EVENTS LARGER THAN MAX_ALLOWED_PACKET 2012-05-21 12:57:39 +05:30
combinations WL#4350 Options in my.cnf style config file should not start with -- 2008-09-05 15:31:09 +02:00
my.cnf Fix comment 2008-04-08 10:11:07 +02:00
README copy from test-extra-5.1 to main tree 2007-02-06 13:35:54 +01:00
rpl_1slave_base.cnf BUG#40257: Please remove --loose-skip-innodb from suite/rpl/rpl_1slave_base.cnf 2008-11-04 18:07:14 +01:00

How to run.
===========

./mysql-test-run.pl --suite=rpl --mysqld=--binlog-format=mixed