Browse Source

MDEV-15238 rpl.perf_buildin_semisync_issue40 sporadically fails on BB

The test was used to result in mismatch due to unaccounted specifics
of the master-slave handshake protocol that sets the Slave_IO_Running
status to true while the semisync master status is set to active a bit later.

The test is refined to expect that.
pull/596/head
Andrei Elkin 8 years ago
parent
commit
7bcf5e2907
  1. 0
      mysql-test/suite/rpl/r/rpl_semisync_ali_issues.result
  2. 0
      mysql-test/suite/rpl/t/rpl_semisync_ali_issues-master.opt
  3. 0
      mysql-test/suite/rpl/t/rpl_semisync_ali_issues-slave.opt
  4. 4
      mysql-test/suite/rpl/t/rpl_semisync_ali_issues.test

0
mysql-test/suite/rpl/r/perf_buildin_semisync_issue40.result → mysql-test/suite/rpl/r/rpl_semisync_ali_issues.result

0
mysql-test/suite/rpl/t/perf_buildin_semisync_issue40-master.opt → mysql-test/suite/rpl/t/rpl_semisync_ali_issues-master.opt

0
mysql-test/suite/rpl/t/perf_buildin_semisync_issue40-slave.opt → mysql-test/suite/rpl/t/rpl_semisync_ali_issues-slave.opt

4
mysql-test/suite/rpl/t/perf_buildin_semisync_issue40.test → mysql-test/suite/rpl/t/rpl_semisync_ali_issues.test

@ -210,6 +210,10 @@ START SLAVE IO_THREAD;
--source include/wait_for_slave_io_to_start.inc
connection con1;
--let $status_var= Rpl_semi_sync_master_status
--let $status_var_value=ON
--source include/wait_for_status_var.inc
SET GLOBAL rpl_semi_sync_master_timeout= 10000000;
SET GLOBAL rpl_semi_sync_master_wait_no_slave= 1;
INSERT INTO t1 values (4);
Loading…
Cancel
Save