mirror of
https://github.com/MariaDB/server.git
synced 2025-08-31 22:22:30 +03:00
cc05440836
Some of the test cases reference to binlog position and these position numbers are written into result explicitly. It is difficult to maintain if log event format changes. There are a couple of cases explicit position number appears, we handle them in different ways A. 'CHANGE MASTER ...' with MASTER_LOG_POS or/and RELAY_LOG_POS options Use --replace_result to mask them. B. 'SHOW BINLOG EVENT ...' Replaced by show_binlog_events.inc or wait_for_binlog_event.inc. show_binlog_events.inc file's function is enhanced by given $binlog_file and $binlog_limit. C. 'SHOW SLAVE STATUS', 'show_slave_status.inc' and 'show_slave_status2.inc' For the test cases just care a few items in the result of 'SHOW SLAVE STATUS', only the items related to each test case are showed. 'show_slave_status.inc' is rebuild, only the given items in $status_items will be showed. 'check_slave_is_running.inc' and 'check_slave_no_error.inc' and 'check_slave_param.inc' are auxiliary files helping to show running status and error information easily.
79 lines
2.0 KiB
Plaintext
79 lines
2.0 KiB
Plaintext
--source include/have_ndb.inc
|
|
--source include/ndb_master-slave.inc
|
|
|
|
connection master;
|
|
CREATE TABLE t1 (a int key, b int) ENGINE=NDB;
|
|
sync_slave_with_master;
|
|
SHOW TABLES;
|
|
|
|
# Lose the events from the slave binary log: there is no
|
|
# need to re-create the table on the master.
|
|
connection slave;
|
|
RESET MASTER;
|
|
|
|
# Insert some values on the slave and master
|
|
connection master;
|
|
INSERT INTO t1 VALUES (1,2);
|
|
# Switch to slave once event is applied and insert a row
|
|
sync_slave_with_master;
|
|
connection slave;
|
|
INSERT INTO t1 VALUES (2,3);
|
|
|
|
# ... it is now very probable that we have a mixed event in the binary
|
|
# log. If we don't, the test should still pass, but will not test the
|
|
# mixed event situation.
|
|
|
|
# The statement is disabled since it cannot reliably show the same
|
|
# info all the time. Use it for debug purposes.
|
|
|
|
#SHOW BINLOG EVENTS;
|
|
|
|
# Replicate back to the master to test this mixed event on the master
|
|
STOP SLAVE;
|
|
|
|
connection master;
|
|
--replace_result $SLAVE_MYPORT SLAVE_PORT
|
|
eval CHANGE MASTER TO MASTER_HOST="127.0.0.1",MASTER_PORT=$SLAVE_MYPORT,MASTER_USER="root";
|
|
|
|
START SLAVE;
|
|
|
|
connection slave;
|
|
sync_slave_with_master master;
|
|
|
|
# The statement is disabled since it cannot reliably show the same
|
|
# info all the time. Use it for debug purposes.
|
|
|
|
#SHOW BINLOG EVENTS;
|
|
|
|
# Check that there is no error in replication
|
|
source include/check_slave_is_running.inc;
|
|
|
|
# Check that we have the data on the master
|
|
SELECT * FROM t1 ORDER BY a;
|
|
|
|
# We should now have another mixed event, likely with "slave" server
|
|
# id last, and with the STMT_END_F flag set.
|
|
|
|
# The statement is disabled since it cannot reliably show the same
|
|
# info all the time. Use it for debug purposes.
|
|
|
|
#SHOW BINLOG EVENTS;
|
|
|
|
# now lets see that this data is applied correctly on the slave
|
|
STOP SLAVE;
|
|
save_master_pos;
|
|
|
|
connection slave;
|
|
START SLAVE;
|
|
|
|
# check that we have the data on the slave
|
|
sync_with_master;
|
|
SELECT * FROM t1 ORDER BY a;
|
|
|
|
# Check that there is no error in replication
|
|
source include/check_slave_is_running.inc;
|
|
|
|
-- connection master
|
|
DROP TABLE t1;
|
|
-- sync_slave_with_master
|