mirror of
https://github.com/MariaDB/server.git
synced 2025-05-11 13:21:44 +03:00
744580d5a7
The IO thread can report error code 2013 into the error log when it is stopped during the initial connection process to the primary, as well as when trying to read an event. However, because the IO thread is being stopped, its connection to the primary is force-killed by the signaling thread (see THD::awake_no_mutex()), and thereby these connection errors should be ignored. Reviewed By: ============ Kristian Nielsen <knielsen@knielsen-hq.org>
32 lines
781 B
Plaintext
32 lines
781 B
Plaintext
#
|
|
# MDEV-8345 STOP SLAVE should not cause an ERROR to be logged to the error log
|
|
#
|
|
source include/have_binlog_format_mixed.inc; # don't repeat the test three times
|
|
source include/master-slave.inc;
|
|
|
|
connection master;
|
|
sync_slave_with_master;
|
|
|
|
--let $iter=100
|
|
--echo # MDEV-32892: Repeatedly starting/stopping io_thread..
|
|
--disable_query_log
|
|
while ($iter)
|
|
{
|
|
stop slave io_thread;
|
|
start slave io_thread;
|
|
--dec $iter
|
|
}
|
|
--enable_query_log
|
|
source include/stop_slave.inc;
|
|
|
|
let SEARCH_FILE=$MYSQLTEST_VARDIR/tmp/slave_log.err;
|
|
let SEARCH_PATTERN=Error reading packet from server: Lost connection;
|
|
source include/search_pattern_in_file.inc;
|
|
|
|
let SEARCH_PATTERN=error code: 2013;
|
|
source include/search_pattern_in_file.inc;
|
|
|
|
source include/start_slave.inc;
|
|
source include/rpl_end.inc;
|
|
|