mirror of
https://github.com/MariaDB/server.git
synced 2025-04-22 15:15:41 +02:00
7af50e4df4
rpl_semi_sync_slave_enabled_consistent.test and the first part of
the commit message comes from Brandon Nesterenko.
A test to show how to induce the "Read semi-sync reply magic number
error" message on a primary. In short, if semi-sync is turned on
during the hand-shake process between a primary and replica, but
later a user negates the rpl_semi_sync_slave_enabled variable while
the replica's IO thread is running; if the io thread exits, the
replica can skip a necessary call to kill_connection() in
repl_semisync_slave.slave_stop() due to its reliance on a global
variable. Then, the replica will send a COM_QUIT packet to the
primary on an active semi-sync connection, causing the magic number
error.
The test in this patch exits the IO thread by forcing an error;
though note a call to STOP SLAVE could also do this, but it ends up
needing more synchronization. That is, the STOP SLAVE command also
tries to kill the VIO of the replica, which makes a race with the IO
thread to try and send the COM_QUIT before this happens (which would
need more debug_sync to get around). See THD::awake_no_mutex for
details as to the killing of the replica’s vio.
Notes:
- The MariaDB documentation does not make it clear that when one
enables semi-sync replication it does not matter if one enables
it first in the master or slave. Any order works.
Changes done:
- The rpl_semi_sync_slave_enabled variable is now a default value for
when semisync is started. The variable does not anymore affect
semisync if it is already running. This fixes the original reported
bug. Internally we now use repl_semisync_slave.get_slave_enabled()
instead of rpl_semi_sync_slave_enabled. To check if semisync is
active on should check the @@rpl_semi_sync_slave_status variable (as
before).
- The semisync protocol conflicts in the way that the original
MySQL/MariaDB client-server protocol was designed (client-server
send and reply packets are strictly ordered and includes a packet
number to allow one to check if a packet is lost). When using
semi-sync the master and slave can send packets at 'any time', so
packet numbering does not work. The 'solution' has been that each
communication starts with packet number 1, but in some cases there
is still a chance that the packet number check can fail. Fixed by
adding a flag (pkt_nr_can_be_reset) in the NET struct that one can
use to signal that packet number checking should not be done. This
is flag is set when semi-sync is used.
- Added Master_info::semi_sync_reply_enabled to allow one to configure
some slaves with semisync and other other slaves without semisync.
Removed global variable semi_sync_need_reply that would not work
with multi-master.
- Repl_semi_sync_master::report_reply_packet() can now recognize
the COM_QUIT packet from semisync slave and not give a
"Read semi-sync reply magic number error" error for this case.
The slave will be removed from the Ack listener.
- On Windows, don't stop semisync Ack listener just because one
slave connection is using socket_id > FD_SETSIZE.
- Removed busy loop in Ack_receiver::run() by using
"Self-pipe trick" to signal new slave and stop Ack_receiver.
- Changed some Repl_semi_sync_slave functions that always returns 0
from int to void.
- Added Repl_semi_sync_slave::slave_reconnect().
- Removed dummy_function Repl_semi_sync_slave::reset_slave().
- Removed some duplicate semisync notes from the error log.
- Add test of "if (get_slave_enabled() && semi_sync_need_reply)"
before calling Repl_semi_sync_slave::slave_reply().
(Speeds up the code as we can skip all initializations).
- If epl_semisync_slave.slave_reply() fails, we disable semisync
for that connection.
- We do not call semisync.switch_off() if there are no active slaves.
Instead we check in Repl_semi_sync_master::commit_trx() if there are
no active threads. This simplices the code.
- Changed assert() to DBUG_ASSERT() to ensure that the DBUG log is
flushed in case of asserts.
- Removed the internal rpl_semi_sync_slave_status as it is not needed
anymore. The @@rpl_semi_sync_slave_status status variable is now
mapped to rpl_semi_sync_enabled.
- Removed rpl_semi_sync_slave_enabled as it is not needed anymore.
Repl_semi_sync_slave::get_slave_enabled() contains the active status.
- Added checking that we do not add a slave twice with
Ack_receiver::add_slave(). This could happen with old code.
- Removed Repl_semi_sync_master::check_and_switch() as it is not
needed anymore.
- Ensure that when we call Ack_receiver::remove_slave() that the slave
is removed from the listener before function returns.
- Call listener.listen_on_sockets() outside of mutex for better
performance and less contested mutex.
- Ensure that listening is ignoring newly added slaves when checking for
responses.
- Fixed the master ack_receiver listener is not killed if there are no
connected slaves (and thus stop semisync handling of future
connections). This could happen if all slaves sockets where would be
marked as unreliable.
- Added unlink() to base_ilist_iterator and remove() to
I_List_iterator. This enables us to remove 'dead' slaves in
Ack_recever::run().
- kill_zombie_dump_threads() now does killing of dump threads properly.
- It can now kill several threads (should be impossible but could
happen if IO slaves reconnects very fast).
- We now wait until the dump thread is done before starting the
dump.
- Added an error if kill_zombie_dump_threads() fails.
- Set thd->variables.server_id before calling
kill_zombie_dump_threads(). This simplies the code.
- Added a lot of comments both in code and tests.
- Removed DBUG_EVALUATE_IF "failed_slave_start" as it is not used.
Test changes:
- rpl.rpl_session_var2 added which runs rpl.rpl_session_var test with
semisync enabled.
- Some timings changed slight with startup of slave which caused
rpl_binlog_dump_slave_gtid_state_info.text to fail as it checked the
error log file before the slave had started properly. Fixed by
adding wait_for_pattern_in_file.inc that allows waiting for the
pattern to appear in the log file.
- Tests have been updated so that we first set
rpl_semi_sync_master_enabled on the master and then set
rpl_semi_sync_slave_enabled on the slaves (this is according to how
the MariaDB documentation document how to setup semi-sync).
- Error text "Master server does not have semi-sync enabled" has been
replaced with "Master server does not support semi-sync" for the
case when the master supports semi-sync but semi-sync is not
enabled.
Other things:
- Some trivial cleanups in Repl_semi_sync_master::update_sync_header().
- We should in 11.3 changed the default value for
rpl-semi-sync-master-wait-no-slave from TRUE to FALSE as the TRUE
does not make much sense as default. The main difference with using
FALSE is that we do not wait for semisync Ack if there are no slave
threads. In the case of TRUE we wait once, which did not bring any
notable benefits except slower startup of master configured for
using semisync.
Co-author: Brandon Nesterenko <brandon.nesterenko@mariadb.com>
This solves the problem reported in MDEV-32960 where a new
slave may not be registered in time and the master disables
semi sync because of that.
162 lines
5.2 KiB
Text
162 lines
5.2 KiB
Text
--source include/have_debug.inc
|
|
--source include/have_debug_sync.inc
|
|
--source include/have_binlog_format_row.inc
|
|
--source include/have_innodb.inc
|
|
--source include/master-slave.inc
|
|
|
|
connection master;
|
|
set @old_master_binlog_checksum= @@global.binlog_checksum;
|
|
|
|
# MDEV-4475: Cannot replicate to old server when binlog contains
|
|
# empty Gtid_list event
|
|
#
|
|
# Test this by binlog rotation before we log any GTIDs.
|
|
sync_slave_with_master;
|
|
--source include/stop_slave.inc
|
|
--echo # Test slave with no capability gets dummy event, which is ignored.
|
|
set @old_dbug= @@global.debug_dbug;
|
|
SET @@global.debug_dbug='+d,simulate_slave_capability_none';
|
|
--source include/start_slave.inc
|
|
|
|
connection master;
|
|
FLUSH LOGS;
|
|
--source include/wait_for_binlog_checkpoint.inc
|
|
CREATE TABLE t1 (a INT PRIMARY KEY);
|
|
INSERT INTO t1 VALUES (0);
|
|
sync_slave_with_master;
|
|
|
|
connection master;
|
|
# Add a dummy event just to have something to sync_slave_with_master on.
|
|
# Otherwise we occasionally get different $relaylog_start, depending on
|
|
# whether Format_description_log_event was written to relay log or not
|
|
# at the time of SHOW SLAVE STATUS.
|
|
ALTER TABLE t1 ORDER BY a;
|
|
sync_slave_with_master;
|
|
connection slave;
|
|
let $relaylog_start= query_get_value(SHOW SLAVE STATUS, Relay_Log_Pos, 1);
|
|
|
|
connection master;
|
|
SET SESSION binlog_annotate_row_events = ON;
|
|
let $binlog_file= query_get_value(SHOW MASTER STATUS, File, 1);
|
|
let $binlog_start= query_get_value(SHOW MASTER STATUS, Position, 1);
|
|
# A short event, to test when we need to use user_var_event for dummy event.
|
|
DELETE FROM t1;
|
|
INSERT INTO t1 /* A comment just to make the annotate event sufficiently long that the dummy event will need to get padded with spaces so that we can test that this works */ VALUES(1);
|
|
let $binlog_limit= 0, 10;
|
|
--source include/show_binlog_events.inc
|
|
sync_slave_with_master;
|
|
connection slave;
|
|
|
|
SELECT * FROM t1;
|
|
let $binlog_file= query_get_value(SHOW SLAVE STATUS, Relay_Log_File, 1);
|
|
let $binlog_start= $relaylog_start;
|
|
let $binlog_limit=0,10;
|
|
--source include/show_relaylog_events.inc
|
|
set @@global.debug_dbug= @old_dbug;
|
|
|
|
--echo # Test dummy event is checksummed correctly.
|
|
|
|
connection master;
|
|
set @@global.binlog_checksum = CRC32;
|
|
--source include/wait_for_binlog_checkpoint.inc
|
|
TRUNCATE t1;
|
|
let $binlog_file= query_get_value(SHOW MASTER STATUS, File, 1);
|
|
let $binlog_start= query_get_value(SHOW MASTER STATUS, Position, 1);
|
|
INSERT INTO t1 VALUES(2);
|
|
let $binlog_limit= 0, 5;
|
|
--source include/show_binlog_events.inc
|
|
sync_slave_with_master;
|
|
connection slave;
|
|
|
|
SELECT * FROM t1;
|
|
let $binlog_file= query_get_value(SHOW SLAVE STATUS, Relay_Log_File, 1);
|
|
let $binlog_start= 0;
|
|
let $binlog_limit=7,5;
|
|
--source include/show_relaylog_events.inc
|
|
|
|
|
|
--echo *** MDEV-5754: MySQL 5.5 slaves cannot replicate from MariaDB 10.0 ***
|
|
|
|
# The problem was that for a group commit, we get commit id into the
|
|
# GTID event, and there was a bug in the code that replaces GTID with
|
|
# dummy that failed when commit id was present.
|
|
#
|
|
# So setup a group commit in InnoDB.
|
|
|
|
--connection master
|
|
CREATE TABLE t2 (a INT PRIMARY KEY) ENGINE=InnoDB;
|
|
# MDEV-515 takes X-lock on the table for the first insert.
|
|
# So concurrent insert won't happen on the table
|
|
INSERT INTO t2 VALUES(100);
|
|
let $binlog_file= query_get_value(SHOW MASTER STATUS, File, 1);
|
|
let $binlog_start= query_get_value(SHOW MASTER STATUS, Position, 1);
|
|
|
|
--connect (con1,127.0.0.1,root,,test,$SERVER_MYPORT_1,)
|
|
SET debug_sync='commit_after_release_LOCK_prepare_ordered SIGNAL master_queued1 WAIT_FOR master_cont1';
|
|
send INSERT INTO t2 VALUES (1);
|
|
|
|
--connection master
|
|
SET debug_sync='now WAIT_FOR master_queued1';
|
|
|
|
--connect (con2,127.0.0.1,root,,test,$SERVER_MYPORT_1,)
|
|
SET debug_sync='commit_after_release_LOCK_prepare_ordered SIGNAL master_queued2';
|
|
send INSERT INTO t2 VALUES (2);
|
|
|
|
--connection master
|
|
SET debug_sync='now WAIT_FOR master_queued2';
|
|
SET debug_sync='now SIGNAL master_cont1';
|
|
|
|
--connection con1
|
|
REAP;
|
|
SET debug_sync='RESET';
|
|
--connection con2
|
|
REAP;
|
|
SET debug_sync='RESET';
|
|
--connection master
|
|
SET debug_sync='RESET';
|
|
let $binlog_limit= 0, 10;
|
|
--source include/show_binlog_events.inc
|
|
--save_master_pos
|
|
|
|
--connection slave
|
|
--sync_with_master
|
|
SELECT * FROM t2 ORDER BY a;
|
|
|
|
|
|
--echo # Test that slave which cannot tolerate holes in binlog stream but
|
|
--echo # knows the event does not get dummy event
|
|
|
|
--source include/stop_slave.inc
|
|
SET @@global.debug_dbug='+d,simulate_slave_capability_old_53';
|
|
--source include/start_slave.inc
|
|
connection master;
|
|
ALTER TABLE t1 ORDER BY a;
|
|
sync_slave_with_master;
|
|
connection slave;
|
|
let $relaylog_start= query_get_value(SHOW SLAVE STATUS, Relay_Log_Pos, 1);
|
|
|
|
connection master;
|
|
let $binlog_file= query_get_value(SHOW MASTER STATUS, File, 1);
|
|
let $binlog_start= query_get_value(SHOW MASTER STATUS, Position, 1);
|
|
UPDATE t1 SET a = 3;
|
|
let $binlog_limit= 0, 5;
|
|
--source include/show_binlog_events.inc
|
|
sync_slave_with_master;
|
|
connection slave;
|
|
|
|
SELECT * FROM t1;
|
|
let $binlog_file= query_get_value(SHOW SLAVE STATUS, Relay_Log_File, 1);
|
|
let $binlog_start= $relaylog_start;
|
|
let $binlog_limit=0,5;
|
|
--source include/show_relaylog_events.inc
|
|
|
|
select @@global.log_slave_updates;
|
|
select @@global.replicate_annotate_row_events;
|
|
|
|
--echo Clean up.
|
|
connection master;
|
|
set @@global.binlog_checksum = @old_master_binlog_checksum;
|
|
DROP TABLE t1, t2;
|
|
sync_slave_with_master;
|
|
set @@global.debug_dbug= @old_dbug;
|
|
--source include/rpl_end.inc
|