mirror of
https://github.com/MariaDB/server.git
synced 2025-01-21 22:34:18 +01:00
df3b1a54f4
* A more dynamic binlog format which allows small changes (1064) * Log session variables in Query_log_event (1063) It contains a few bugfixes (which I made when running the testsuite). I carefully updated the results of the testsuite (i.e. I checked for every one, if the difference between .reject and .result could be explained). Apparently mysql-test-run --manager is broken in 4.1 and 5.0 currently, so I could neither run the few tests which require --manager, nor check that they pass nor modify their .result. But for builds, we don't run with --manager. Apart from --manager, the full testsuite passes, with Valgrind too (no errors). I'm going to push in the next minutes. Remains: update the manual. Note: by chance I saw that (in 4.1, in 5.0) rpl_get_lock fails when run alone; this is normal at it makes assumptions on thread ids. I will fix this one day in 4.1.
93 lines
2.6 KiB
Text
93 lines
2.6 KiB
Text
# Test of options max_binlog_size and max_relay_log_size and
|
|
# how they act (if max_relay_log_size == 0, use max_binlog_size
|
|
# for relay logs too).
|
|
# Test of manual relay log rotation with FLUSH LOGS.
|
|
|
|
source include/master-slave.inc;
|
|
connection slave;
|
|
stop slave;
|
|
connection master;
|
|
# Generate a big enough master's binlog to cause relay log rotations
|
|
create table t1 (a int);
|
|
let $1=800;
|
|
disable_query_log;
|
|
begin;
|
|
while ($1)
|
|
{
|
|
# eval means expand $ expressions
|
|
eval insert into t1 values( $1 );
|
|
dec $1;
|
|
}
|
|
enable_query_log;
|
|
drop table t1;
|
|
save_master_pos;
|
|
connection slave;
|
|
reset slave;
|
|
set global max_binlog_size=8192;
|
|
set global max_relay_log_size=8192-1; # mapped to 4096
|
|
select @@global.max_relay_log_size;
|
|
start slave;
|
|
sync_with_master;
|
|
--replace_result $MASTER_MYPORT MASTER_PORT 3306 MASTER_PORT 3334 MASTER_PORT
|
|
--replace_column 1 # 8 # 9 # 23 # 33 #
|
|
show slave status;
|
|
stop slave;
|
|
reset slave;
|
|
set global max_relay_log_size=(5*4096);
|
|
select @@global.max_relay_log_size;
|
|
start slave;
|
|
sync_with_master;
|
|
--replace_result $MASTER_MYPORT MASTER_PORT 3306 MASTER_PORT 3334 MASTER_PORT
|
|
--replace_column 1 # 8 # 9 # 23 # 33 #
|
|
show slave status;
|
|
stop slave;
|
|
reset slave;
|
|
set global max_relay_log_size=0;
|
|
select @@global.max_relay_log_size;
|
|
start slave;
|
|
sync_with_master;
|
|
--replace_result $MASTER_MYPORT MASTER_PORT 3306 MASTER_PORT 3334 MASTER_PORT
|
|
--replace_column 1 # 8 # 9 # 23 # 33 #
|
|
show slave status;
|
|
|
|
# Tests below are mainly to ensure that we have not coded with wrong assumptions
|
|
|
|
stop slave;
|
|
reset slave;
|
|
# test of relay log rotation when the slave is stopped
|
|
# (to make sure it does not crash).
|
|
flush logs;
|
|
--replace_result $MASTER_MYPORT MASTER_PORT 3306 MASTER_PORT 3334 MASTER_PORT
|
|
--replace_column 1 # 8 # 9 # 23 # 33 #
|
|
show slave status;
|
|
|
|
reset slave;
|
|
start slave;
|
|
sync_with_master;
|
|
# test of relay log rotation when the slave is started
|
|
flush logs;
|
|
# We have now easy way to be sure that the SQL thread has now deleted the
|
|
# log we just closed. But a trick to achieve this is do an update on the master.
|
|
connection master;
|
|
create table t1 (a int);
|
|
save_master_pos;
|
|
connection slave;
|
|
sync_with_master;
|
|
--replace_result $MASTER_MYPORT MASTER_PORT 3306 MASTER_PORT 3334 MASTER_PORT
|
|
--replace_column 1 # 8 # 9 # 23 # 33 #
|
|
show slave status;
|
|
# one more rotation, to be sure Relay_Log_Space is correctly updated
|
|
flush logs;
|
|
connection master;
|
|
drop table t1;
|
|
save_master_pos;
|
|
connection slave;
|
|
sync_with_master;
|
|
--replace_result $MASTER_MYPORT MASTER_PORT 3306 MASTER_PORT 3334 MASTER_PORT
|
|
--replace_column 1 # 8 # 9 # 23 # 33 #
|
|
show slave status;
|
|
|
|
connection master;
|
|
# test that the absence of relay logs does not make a master crash
|
|
flush logs;
|
|
show master status;
|