mirror of
https://github.com/MariaDB/server.git
synced 2025-01-18 04:53:01 +01:00
0b8743c1b2
while the slave is connected. mysql-test/t/rpl_trunc_binlog.test: don't RESET MASTER while the slave is connected; this could confuse the master or slave. (In replication you don't RESET MASTER while a slave is connected!) sql/slave.cc: typo
24 lines
866 B
Text
24 lines
866 B
Text
# We are testing if a binlog which contains BEGIN but not COMMIT (the master did
|
|
# while writing the transaction to the binlog) triggers an error on slave.
|
|
# So we use such a truncated binlog and simulate that the master restarted after
|
|
# this.
|
|
|
|
source include/master-slave.inc;
|
|
|
|
connection slave;
|
|
# If we are not supporting transactions in the slave, the unfinished transaction
|
|
# won't cause any error, so we need to skip the test. In the 4.0 testsuite, the
|
|
# slave always runs without InnoDB, so we check for BDB.
|
|
source include/have_bdb.inc;
|
|
stop slave;
|
|
connection master;
|
|
flush logs;
|
|
system mv -f var/log/master-bin.001 var/log/master-bin.002;
|
|
system cp std_data/trunc_binlog.001 var/log/master-bin.001;
|
|
connection slave;
|
|
reset slave;
|
|
start slave;
|
|
# can't sync_with_master so we must sleep
|
|
sleep 3;
|
|
--replace_result $MASTER_MYPORT MASTER_PORT
|
|
show slave status;
|