mariadb/mysql-test/suite/rpl/r/rpl_heartbeat_2slaves.result
Serge Kozlov 4c9cb95c2e Bug#43828, Bug#59494.
After introducing new way of initialization of replication the setting different heartbeat periods for slaves was missed.
Added asserts
2011-02-04 22:07:48 +03:00

41 lines
1.1 KiB
Text

include/rpl_init.inc [topology=1->2,1->3]
include/rpl_connect.inc [creating master]
include/rpl_connect.inc [creating slave_1]
include/rpl_connect.inc [creating slave_2]
include/stop_slave.inc
CHANGE MASTER TO MASTER_HEARTBEAT_PERIOD = 0.1;
include/start_slave.inc
include/stop_slave.inc
CHANGE MASTER TO MASTER_HEARTBEAT_PERIOD = 1;
include/start_slave.inc
Slave has received heartbeat event
include/assert.inc [slave_1 should have received more heartbeats than slave_2]
include/rpl_stop_slaves.inc
include/rpl_change_topology.inc [new topology=1->3->2]
include/rpl_start_slaves.inc
include/stop_slave.inc
CHANGE MASTER TO MASTER_HEARTBEAT_PERIOD=0.1;
include/start_slave.inc
slave_1 has received heartbeat event
[on master]
CREATE TABLE t1 (a INT PRIMARY KEY, b VARCHAR(10), c LONGTEXT);
INSERT INTO t1 VALUES (1, 'on master', '');
SHOW TABLES;
Tables_in_test
t1
[on slave_2]
SHOW TABLES;
Tables_in_test
t1
[on slave_1]
SHOW TABLES;
Tables_in_test
[on master]
creating updates on master and send to slave_2 during 5 second
[on slave_1]
include/assert.inc [slave_1 should have received heartbeats]
*** Clean up ***
DROP TABLE t1;
include/rpl_end.inc