MySQL Bugs: #59898: rqg_rpl_semisync test fails sporadically on pb2

Bug #59898	rqg_rpl_semisync test fails sporadically on pb2
Submitted:	2 Feb 2011 17:31	Modified:	14 Mar 2014 19:38
Reporter:	Sandeep Doddaballapur	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	mysql-trunk	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	rqg_pb2

Description:
rqg_rpl_semisync test sporadically fails on pb2 with status stating 
STATUS_REPLICATION_FAILURE (103)

The test fails with reporter ReplicationSemiSync reporting issues with timeouts between slave and master 

Following is the snippet seen in error log 
==============================
# 2011-02-02T13:16:05 GenTest::Reporter::ReplicationSemiSync: Waiting for slave...
# 2011-02-02T13:16:07 GenTest::Reporter::ReplicationSemiSync: ... slave caught up with master.
# 2011-02-02T13:16:07 GenTest::Reporter::ReplicationSemiSync: Flushed status.
# 2011-02-02T13:16:07 GenTest::Reporter::ReplicationSemiSync: stopping slave IO thread.
# 2011-02-02T13:16:09 GenTest::Reporter::ReplicationSemiSync: stopped slave IO thread.
# 2011-02-02T13:16:09 GenTest::Reporter::ReplicationSemiSync: Sleeping for 5 seconds.
# 2011-02-02T13:16:14 GenTest::Reporter::ReplicationSemiSync: Transactions were committed semisynchronously while slave was stopped for less than the timeout.
# 2011-02-02T13:16:14 GenTest::Reporter::ReplicationSemiSync: rpl_semi_sync_master_yes_tx = 1;
# 2011-02-02T13:16:14 Killing child process with pid 485...
# 2011-02-02T13:16:14 Kill GenTest::ErrorFilter(483)
# 2011-02-02T13:16:16 XML report written to /export/home/pb2/test/sb_1-2933660-1296648889.7/tmp/rqg_rpl_semisync.xml
# 2011-02-02T13:16:16 XML Transport type: SCP
# 2011-02-02T13:16:16 SCP command is: scp /export/home/pb2/test/sb_1-2933660-1296648889.7/tmp/rqg_rpl_semisync.xml regin.norway.sun.com:/raid/xml_results/TestTool/xml/
# 2011-02-02T13:16:16 Test completed with failure status STATUS_REPLICATION_FAILURE (103)
# 2011-02-02T13:16:16 GenTest exited with exit status STATUS_REPLICATION_FAILURE (103)

==============================

Following is the link to the log 
http://pb2.norway.sun.com/web.py?action=archive_download&archive_id=2934441&pretty=please

How to repeat:
The issue pops up at very occassions 

Following is the rqg command on pb2 
runall-new.pl \ 
--mysqld=--loose-skip-safemalloc \ 
--gendata=conf/replication/replication_single_engine.zz \ 
--engine=InnoDB \ 
--grammar=conf/replication/replication_simple.yy \ 
--rpl_mode=default \  
--mysqld=--plugin-dir=/export/home/pb2/test/sb_1-2933660-1296648889.7/mysql-5.6.2-m5-linux-i686-test/lib/plugin \ 
--mysqld=--plugin-load=rpl_semi_sync_master=semisync_master.so:rpl_semi_sync_slave=semisync_slave.so \ 
--mysqld=--rpl_semi_sync_master_enabled=1 \ 
--mysqld=--rpl_semi_sync_slave_enabled=1 \ 
--mysqld=--innodb \ 
--reporters=ReplicationSemiSync,Deadlock,Backtrace,ErrorLog \ 
--validators=None \ 
--threads=1 \ 
--duration=300 \ 
--queries=1M \ 
--basedir=/export/home/pb2/test/sb_1-2933660-1296648889.7/mysql-5.6.2-m5-linux-i686-test \ 
--vardir=/export/home/pb2/test/sb_1-2933660-1296648889.7/mysql-5.6.2-m5-linux-i686-test/vardirs \ 
--mysqld=--log-output=file \ 
--mysqld=--loose-table-lock-wait-timeout=1 \ 
--mysqld=--loose-lock-wait-timeout=1 \ 
--mysqld=--loose-innodb-lock-wait-timeout=1 \ 
--testname=rqg_rpl_semisync \ 
--xml-output=/export/home/pb2/test/sb_1-2933660-1296648889.7/tmp/rqg_rpl_semisync.xml \ 
--report-xml-tt \ 
--report-xml-tt-type=scp \ 
--report-xml-tt-dest=regin.norway.sun.com:/raid/xml_results/TestTool/xml/

Similar error seen on a push on 24th Jan

Following is the link 
http://pb2.norway.sun.com/web.py?action=archive_download&archive_id=2873422&pretty=please

Following is the snippet from the log 
=====================================
# 2011-01-24T05:32:32 GenTest::Reporter::ReplicationSemiSync: ... flushed.
# 2011-01-24T05:32:32 GenTest::Reporter::ReplicationSemiSync: Waiting for slave...
# 2011-01-24T05:32:33 GenTest::Reporter::ReplicationSemiSync: ... slave caught up with master.
# 2011-01-24T05:32:33 GenTest::Reporter::ReplicationSemiSync: Flushed status.
# 2011-01-24T05:32:33 GenTest::Reporter::ReplicationSemiSync: stopping slave IO thread.
# 2011-01-24T05:32:35 GenTest::Reporter::ReplicationSemiSync: stopped slave IO thread.
# 2011-01-24T05:32:35 GenTest::Reporter::ReplicationSemiSync: Sleeping for 20 seconds.
# 2011-01-24T05:32:46 Query: INSERT INTO `table0_innodb_int_autoinc` ( `col_char_255_latin1_not_null_key` ) VALUES ( NULL ) failed: 1048 Column '%s' cannot be null. Further errors of this kind will be suppressed.
# 2011-01-24T05:32:55 GenTest::Reporter::ReplicationSemiSync: Transactions were committed semisynchronously while slave was stopped longer than the timeout.
# 2011-01-24T05:32:55 GenTest::Reporter::ReplicationSemiSync: rpl_semi_sync_master_yes_tx = 1;
# 2011-01-24T05:32:55 Killing child process with pid 23588...
# 2011-01-24T05:32:55 Kill GenTest::ErrorFilter(23586)
# 2011-01-24T05:32:56 XML report written to /export/home/pb2/test/sb_1-2872993-1295843469.38/tmp/rqg_rpl_semisync.xml
# 2011-01-24T05:32:56 XML Transport type: SCP
# 2011-01-24T05:32:56 SCP command is: scp /export/home/pb2/test/sb_1-2872993-1295843469.38/tmp/rqg_rpl_semisync.xml regin.norway.sun.com:/raid/xml_results/TestTool/xml/
# 2011-01-24T05:32:56 Test completed with failure status STATUS_REPLICATION_FAILURE (103)
# 2011-01-24T05:32:56 GenTest exited with exit status STATUS_REPLICATION_FAILURE (103)
=====================================

Closed as "Can't repeat", because I have not access to files provided
anymore, error was sporadic and what caused it to happen is unknown. If
you are able to repeat similar failure feel free to reopen the report.