BUG#49978: Replication tests don't clean up replication state at the end
Major replication test framework cleanup. This does the following:
- Ensure that all tests clean up the replication state when they
finish, by making check-testcase check the output of SHOW SLAVE STATUS.
This implies:
- Slave must not be running after test finished. This is good
because it removes the risk for sporadic errors in subsequent
tests when a test forgets to sync correctly.
- Slave SQL and IO errors must be cleared when test ends. This is
good because we will notice if a test gets an unexpected error in
the slave threads near the end.
- We no longer have to clean up before a test starts.
- Ensure that all tests that wait for an error in one of the slave
threads waits for a specific error. It is no longer possible to
source wait_for_slave_[sql|io]_to_stop.inc when there is an error
in one of the slave threads. This is good because:
- If a test expects an error but there is a bug that causes
another error to happen, or if it stops the slave thread without
an error, then we will notice.
- When developing tests, wait_for_*_to_[start|stop].inc will fail
immediately if there is an error in the relevant slave thread.
Before this patch, we had to wait for the timeout.
- Remove duplicated and repeated code for setting up unusual replication
topologies. Now, there is a single file that is capable of setting
up arbitrary topologies (include/rpl_init.inc, but
include/master-slave.inc is still available for the most common
topology). Tests can now end with include/rpl_end.inc, which will clean
up correctly no matter what topology is used. The topology can be
changed with include/rpl_change_topology.inc.
- Improved debug information when tests fail. This includes:
- debug info is printed on all servers configured by include/rpl_init.inc
- User can set $rpl_debug=1, which makes auxiliary replication files
print relevant debug info.
- Improved documentation for all auxiliary replication files. Now they
describe purpose, usage, parameters, and side effects.
- Many small code cleanups:
- Made have_innodb.inc output a sensible error message.
- Moved contents of rpl000017-slave.sh into rpl000017.test
- Added mysqltest variables that expose the current state of
disable_warnings/enable_warnings and friends.
- Too many to list here: see per-file comments for details.
2010-12-19 18:07:28 +01:00
|
|
|
# ==== Purpose ====
|
|
|
|
#
|
|
|
|
# Stop the server given by $rpl_server_number.
|
|
|
|
#
|
|
|
|
# ==== Usage ====
|
|
|
|
#
|
|
|
|
# --let $rpl_server_number= N
|
|
|
|
# [--let $rpl_debug= 1]
|
|
|
|
# --source include/rpl_stop_server.inc
|
|
|
|
#
|
|
|
|
# Parameters:
|
|
|
|
#
|
|
|
|
# $rpl_server_number
|
|
|
|
# Number to identify the server that needs to reconnect. 1 is the
|
|
|
|
# master server, 2 the slave server, 3 the 3rd server, and so on.
|
|
|
|
# Cf. include/rpl_init.inc
|
|
|
|
#
|
|
|
|
# $rpl_debug
|
|
|
|
# See include/rpl_init.inc
|
|
|
|
#
|
|
|
|
# ==== See also ====
|
|
|
|
#
|
|
|
|
# rpl_start_server.inc
|
|
|
|
# rpl_restart_server.inc
|
|
|
|
|
|
|
|
|
|
|
|
# Can't use begin_include_file / end_include_file because they require
|
|
|
|
# executing on a server and the server will go down after this script.
|
|
|
|
if (!$_include_file_depth)
|
|
|
|
{
|
|
|
|
--echo include/rpl_stop_server.inc [server_number=$rpl_server_number]
|
|
|
|
}
|
|
|
|
--inc $_include_file_depth
|
|
|
|
--let $_rpl_stop_server_old_connection= $CURRENT_CONNECTION
|
|
|
|
if ($rpl_debug)
|
|
|
|
{
|
|
|
|
--echo $_include_file_indent con='$CURRENT_CONNECTION' warn='$ENABLED_WARNINGS' qlog='$ENABLED_QUERY_LOG' rlog='$ENABLED_RESULT_LOG' aborterr='$ENABLED_ABORT_ON_ERROR'
|
|
|
|
--echo $_include_file_indent==== BEGIN include/$include_filename ====
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
--let $rpl_connection_name= server_$rpl_server_number
|
|
|
|
--source include/rpl_connection.inc
|
|
|
|
|
|
|
|
# Write file to make mysql-test-run.pl expect the "crash", but don't start
|
|
|
|
# it until it's told to
|
2011-01-18 12:25:07 +01:00
|
|
|
--exec echo "wait" > $MYSQLTEST_VARDIR/tmp/mysqld.$rpl_server_number.expect
|
BUG#49978: Replication tests don't clean up replication state at the end
Major replication test framework cleanup. This does the following:
- Ensure that all tests clean up the replication state when they
finish, by making check-testcase check the output of SHOW SLAVE STATUS.
This implies:
- Slave must not be running after test finished. This is good
because it removes the risk for sporadic errors in subsequent
tests when a test forgets to sync correctly.
- Slave SQL and IO errors must be cleared when test ends. This is
good because we will notice if a test gets an unexpected error in
the slave threads near the end.
- We no longer have to clean up before a test starts.
- Ensure that all tests that wait for an error in one of the slave
threads waits for a specific error. It is no longer possible to
source wait_for_slave_[sql|io]_to_stop.inc when there is an error
in one of the slave threads. This is good because:
- If a test expects an error but there is a bug that causes
another error to happen, or if it stops the slave thread without
an error, then we will notice.
- When developing tests, wait_for_*_to_[start|stop].inc will fail
immediately if there is an error in the relevant slave thread.
Before this patch, we had to wait for the timeout.
- Remove duplicated and repeated code for setting up unusual replication
topologies. Now, there is a single file that is capable of setting
up arbitrary topologies (include/rpl_init.inc, but
include/master-slave.inc is still available for the most common
topology). Tests can now end with include/rpl_end.inc, which will clean
up correctly no matter what topology is used. The topology can be
changed with include/rpl_change_topology.inc.
- Improved debug information when tests fail. This includes:
- debug info is printed on all servers configured by include/rpl_init.inc
- User can set $rpl_debug=1, which makes auxiliary replication files
print relevant debug info.
- Improved documentation for all auxiliary replication files. Now they
describe purpose, usage, parameters, and side effects.
- Many small code cleanups:
- Made have_innodb.inc output a sensible error message.
- Moved contents of rpl000017-slave.sh into rpl000017.test
- Added mysqltest variables that expose the current state of
disable_warnings/enable_warnings and friends.
- Too many to list here: see per-file comments for details.
2010-12-19 18:07:28 +01:00
|
|
|
|
|
|
|
# Send shutdown to the connected server and give
|
|
|
|
# it 10 seconds to die before zapping it
|
|
|
|
shutdown_server 10;
|
|
|
|
|
|
|
|
--source include/wait_until_disconnected.inc
|
|
|
|
|
|
|
|
|
|
|
|
--let $rpl_connection_name= $_rpl_stop_server_old_connection
|
|
|
|
--source include/rpl_connection.inc
|
|
|
|
--dec $_include_file_depth
|
|
|
|
if ($rpl_debug)
|
|
|
|
{
|
|
|
|
--echo $_include_file_indent==== END include/rpl_stop_server.inc [server_number=$rpl_server_number] ====
|
|
|
|
--echo $_include_file_indent con='$CURRENT_CONNECTION' warn='$ENABLED_WARNINGS' qlog='$ENABLED_QUERY_LOG' rlog='$ENABLED_RESULT_LOG' aborterr='$ENABLED_ABORT_ON_ERROR'
|
|
|
|
}
|