Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0.15
-
None
Description
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.