[MDEV-7467] sporadic failure in rpl.rpl_gtid_crash Created: 2015-01-14  Updated: 2015-01-14  Resolved: 2015-01-14

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.0.15
Fix Version/s: 10.0.16

Type: Bug Priority: Major
Reporter: Kristian Nielsen Assignee: Kristian Nielsen
Resolution: Fixed Votes: 0
Labels: None


 Description   

https://buildbot.askmonty.org/buildbot/builders/kvm-dgcov-jaunty-i386/builds/4561/steps/test_2/logs/stdio

rpl.rpl_gtid_crash 'innodb_plugin,mix'   w1 [ fail ]
        Test ended at 2015-01-13 23:17:46
 
CURRENT_TEST: rpl.rpl_gtid_crash
mysqltest: At line 218: query 'START SLAVE' failed: 2013: Lost connection to MySQL server during query
 
The result from queries just before the failure was:
< snip >
SET GLOBAL debug_dbug="+d,inject_crash_before_write_rpl_slave_state";
START SLAVE;
INSERT INTO t1 VALUES (4);
include/save_master_gtid.inc
include/sync_with_master_gtid.inc
include/stop_slave.inc
SET GLOBAL debug_dbug="+d,crash_commit_before";
START SLAVE;
INSERT INTO t1 VALUES (5);
include/save_master_gtid.inc
include/sync_with_master_gtid.inc
include/stop_slave.inc
SET GLOBAL debug_dbug="+d,crash_commit_after";
START SLAVE;
INSERT INTO t1 VALUES (6);
include/save_master_gtid.inc
include/sync_with_master_gtid.inc
include/stop_slave.inc
SET GLOBAL debug_dbug="+d,inject_crash_before_flush_rli";
START SLAVE;

We are deliberately crashing the slave mysqld. Depending on whether the crash
happens before or after the START SLAVE command returns to the client, we can
get this error.



 Comments   
Comment by Kristian Nielsen [ 2015-01-14 ]

http://lists.askmonty.org/pipermail/commits/2015-January/007264.html

Generated at Thu Feb 08 07:19:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.