mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-22 06:44:16 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test/suite/rpl/t/rpl_flushlog_loop.test

78 lines
2 KiB
Text
Raw Normal View History

Portability fixes. Improve mysql-test to be more robust. Fix that GRANT doesn't delete SSL options Change innobase_flush_log_at_trx_commit to uint. Don't rotate logs if we read a rotate log entry from the master.
2002-09-11 06:40:08 +03:00
# Testing if "flush logs" command bouncing resulting in logs created in a loop
# in case of bi-directional replication
WL#1012: All changes as one single changeset. This includes both code and test cases.
2005-12-22 06:39:02 +01:00
-- source include/master-slave.inc
Portability fixes. Improve mysql-test to be more robust. Fix that GRANT doesn't delete SSL options Change innobase_flush_log_at_trx_commit to uint. Don't rotate logs if we read a rotate log entry from the master.
2002-09-11 06:40:08 +03:00
WL#4189 - dynamic configuration support - safe process - cleanups - create new suite for fedarated
2007-12-12 18:19:24 +01:00
let $MYSQLD_DATADIR= `select @@datadir`;
--replace_result $MYSQLD_DATADIR MYSQLD_DATADIR/
Bug#28893 --relay-log variable is not exposed with SHOW VARIABLES added variables relay_log, relay_log_index, relay_log_info_file to init_vars[] to make them visible within SHOW VARIABLES
2007-10-10 12:21:11 +05:00
show variables like 'relay_log%';
Portability fixes. Improve mysql-test to be more robust. Fix that GRANT doesn't delete SSL options Change innobase_flush_log_at_trx_commit to uint. Don't rotate logs if we read a rotate log entry from the master.
2002-09-11 06:40:08 +03:00
connection slave;
WL#1012: All changes as one single changeset. This includes both code and test cases.
2005-12-22 06:39:02 +01:00
--disable_warnings
BUG#11316 mysqltest, problems when assigning value with '#' to $variable - Fixed problem, only detect comment if the # is on start of line AND starting line of the current command. - Wrote tests for most of the mysqltest commands, added stricter checking of correct syntax.
2005-07-15 17:51:43 +02:00
stop slave;
WL#1012: All changes as one single changeset. This includes both code and test cases.
2005-12-22 06:39:02 +01:00
--enable_warnings
Made mysql-test results independent of MASTER_PORT and SLAVE_PORT
2002-09-23 16:34:49 +03:00
--replace_result $MASTER_MYPORT MASTER_PORT
Portability fixes. Improve mysql-test to be more robust. Fix that GRANT doesn't delete SSL options Change innobase_flush_log_at_trx_commit to uint. Don't rotate logs if we read a rotate log entry from the master.
2002-09-11 06:40:08 +03:00
eval change master to master_host='127.0.0.1',master_user='root',
master_password='',master_port=$MASTER_MYPORT;
altered syntax from SLAVE START|STOP to START|STOP SLAVE
2002-10-24 17:46:14 -06:00
start slave;
Made rpl_flushlog_loop use wait_slave_status instead of sleep. This to save 5 seconds of test time. More test to follow. :-)
2006-03-21 17:40:51 +01:00
#
# Start replication slave -> master
#
Portability fixes. Improve mysql-test to be more robust. Fix that GRANT doesn't delete SSL options Change innobase_flush_log_at_trx_commit to uint. Don't rotate logs if we read a rotate log entry from the master.
2002-09-11 06:40:08 +03:00
connection master;
WL#1012: All changes as one single changeset. This includes both code and test cases.
2005-12-22 06:39:02 +01:00
--disable_warnings
stop slave;
--enable_warnings
Made mysql-test results independent of MASTER_PORT and SLAVE_PORT
2002-09-23 16:34:49 +03:00
--replace_result $SLAVE_MYPORT SLAVE_PORT
Portability fixes. Improve mysql-test to be more robust. Fix that GRANT doesn't delete SSL options Change innobase_flush_log_at_trx_commit to uint. Don't rotate logs if we read a rotate log entry from the master.
2002-09-11 06:40:08 +03:00
eval change master to master_host='127.0.0.1',master_user='root',
master_password='',master_port=$SLAVE_MYPORT;
Made rpl_flushlog_loop use wait_slave_status instead of sleep. This to save 5 seconds of test time. More test to follow. :-)
2006-03-21 17:40:51 +01:00
BUG#37975: wait_for_slave_* should increase the timeout Problem 1: tests often fail in pushbuild with a timeout when waiting for the slave to start/stop/receive error. Fix 1: Updated the wait_for_slave_* macros in the following way: - The timeout is increased by a factor ten - Refactored the macros so that wait_for_slave_param does the work for the other macros. Problem 2: Tests are often incorrectly written, lacking a source include/wait_for_slave_to_[start|stop].inc. Fix 2: Improved the chance to get it right by adding include/start_slave.inc and include/stop_slave.inc, and updated tests to use these. Problem 3: The the built-in test language command wait_for_slave_to_stop is a misnomer (does not wait for the slave io thread) and does not give as much debug info in case of failure as the otherwise equivalent macro source include/wait_for_slave_sql_to_stop.inc Fix 3: Replaced all calls to the built-in command by a call to the macro. Problem 4: Some, but not all, of the wait_for_slave_* macros had an implicit connection slave. This made some tests confusing to read, and made it more difficult to use the macro in circular replication scenarios, where the connection named master needs to wait. Fix 4: Removed the implicit connection slave from all wait_for_slave_* macros, and updated tests to use an explicit connection slave where necessary. Problem 5: The macros wait_slave_status.inc and wait_show_pattern.inc were unused. Moreover, using them is difficult and error-prone. Fix 5: remove these macros. Problem 6: log_bin_trust_function_creators_basic failed when running tests because it assumed @@global.log_bin_trust_function_creators=1, and some tests modified this variable without resetting it to its original value. Fix 6: All tests that use this variable have been updated so that they reset the value at end of test.
2008-07-10 18:09:39 +02:00
source include/start_slave.inc;
Made rpl_flushlog_loop use wait_slave_status instead of sleep. This to save 5 seconds of test time. More test to follow. :-)
2006-03-21 17:40:51 +01:00
#
# Flush logs of slave
#
WL#4091, replace sleeps
2008-02-28 14:36:14 +03:00
# Create full loop by following way:
# 1. Insert into t1 on master (1st).
# 2. Insert into t1 on slave (2nd) when the event (1st) for t1 replicated.
# 3. Master waits until the event (2nd) for t1 will be replicated.
--disable_query_log
CREATE TABLE t1 (a INT KEY) ENGINE= MyISAM;
WL#4091, fix for rpl_flushlog_loop for windows platforms
2008-03-02 20:17:39 +03:00
let $wait_binlog_event= CREATE TABLE t1;
--source include/wait_for_binlog_event.inc
WL#4091, enable rpl_flushlog_loop.test and fix for rpl_drop_temp.test
2008-03-01 00:05:23 +03:00
sync_slave_with_master;
wl#4091 improving a test that shows a failure. the wait condition was for data in tables but the log positions are updates after the data are unlocked. So there was a time window [after_table_unlock_for_select, log_pos_updated] where the orig cond was true but log position might be changed. the correct one is to expect the last pos of the slave's insert in the output of show_slave_status on the master.
2008-03-28 18:25:49 +02:00
WL#4091, enable rpl_flushlog_loop.test and fix for rpl_drop_temp.test
2008-03-01 00:05:23 +03:00
connection master;
WL#4091, replace sleeps
2008-02-28 14:36:14 +03:00
INSERT INTO t1 VALUE(1);
--enable_query_log
FLUSH LOGS;
wl#4091 improving a test that shows a failure. the wait condition was for data in tables but the log positions are updates after the data are unlocked. So there was a time window [after_table_unlock_for_select, log_pos_updated] where the orig cond was true but log position might be changed. the correct one is to expect the last pos of the slave's insert in the output of show_slave_status on the master.
2008-03-28 18:25:49 +02:00
let $slave_param_value= query_get_value(SHOW MASTER STATUS, Position, 1);
WL#4091, replace sleeps
2008-02-28 14:36:14 +03:00
connection slave;
wl#4091 improving a test that shows a failure. the wait condition was for data in tables but the log positions are updates after the data are unlocked. So there was a time window [after_table_unlock_for_select, log_pos_updated] where the orig cond was true but log position might be changed. the correct one is to expect the last pos of the slave's insert in the output of show_slave_status on the master.
2008-03-28 18:25:49 +02:00
let $slave_param= Exec_Master_Log_Pos;
source include/wait_for_slave_param.inc;
WL#4091, replace sleeps
2008-02-28 14:36:14 +03:00
--disable_query_log
INSERT INTO t1 VALUE(2);
wl#4091 improving a test that shows a failure. the wait condition was for data in tables but the log positions are updates after the data are unlocked. So there was a time window [after_table_unlock_for_select, log_pos_updated] where the orig cond was true but log position might be changed. the correct one is to expect the last pos of the slave's insert in the output of show_slave_status on the master.
2008-03-28 18:25:49 +02:00
let $slave_param_value= query_get_value(SHOW MASTER STATUS, Position, 1);
WL#4091, replace sleeps
2008-02-28 14:36:14 +03:00
--enable_query_log
wl#4091 improving a test that shows a failure. the wait condition was for data in tables but the log positions are updates after the data are unlocked. So there was a time window [after_table_unlock_for_select, log_pos_updated] where the orig cond was true but log position might be changed. the correct one is to expect the last pos of the slave's insert in the output of show_slave_status on the master.
2008-03-28 18:25:49 +02:00
WL#4091, replace sleeps
2008-02-28 14:36:14 +03:00
connection master;
wl#4091 improving a test that shows a failure. the wait condition was for data in tables but the log positions are updates after the data are unlocked. So there was a time window [after_table_unlock_for_select, log_pos_updated] where the orig cond was true but log position might be changed. the correct one is to expect the last pos of the slave's insert in the output of show_slave_status on the master.
2008-03-28 18:25:49 +02:00
let $slave_param= Exec_Master_Log_Pos;
source include/wait_for_slave_param.inc;
WL#4091, replace sleeps
2008-02-28 14:36:14 +03:00
--enable_query_log
Made rpl_flushlog_loop use wait_slave_status instead of sleep. This to save 5 seconds of test time. More test to follow. :-)
2006-03-21 17:40:51 +01:00
#
# Show status of slave
#
wl#4091 improving a test that shows a failure. the wait condition was for data in tables but the log positions are updates after the data are unlocked. So there was a time window [after_table_unlock_for_select, log_pos_updated] where the orig cond was true but log position might be changed. the correct one is to expect the last pos of the slave's insert in the output of show_slave_status on the master.
2008-03-28 18:25:49 +02:00
--replace_result $SLAVE_MYPORT SLAVE_PORT $slave_param_value POSITION
BUG#24954 (Last_errno and Last_error not set after master_retry_count was reached): Adding new fields Last_{IO,SQL}_Errno and Last_{IO,SQL}_Error to output of SHOW SLAVE STATUS to hold errors from I/O and SQL thread respectively. Old fields Last_Error and Last_Errno are aliases for Last_SQL_Error and Last_SQL_Errno respectively. Fields are added last to output of SHOW SLAVE STATUS to allow old applications to use the same positional arguments into the row, while allowing new application to benefit from the added information. In addition, some new error codes are added (especially for the I/O thread) to be able to provide sensible error message.
2007-06-09 07:19:37 +02:00
--replace_column 1 # 8 # 9 # 16 # 23 # 33 # 34 # 35 #
--query_vertical SHOW SLAVE STATUS
Ensuring that master and slave both issue a RESET MASTER and RESET SLAVE when resetting replication tests. If not, circular replication setups will leave cruft in the slaves binary log.
2008-07-09 14:34:00 +02:00
--disable_query_log
connection master;
DROP TABLE t1;
sync_slave_with_master;
--enable_query_log
Reference in a new issue Copy permalink