Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.6.18, 10.11.8, 11.0(EOL)
-
None
Description
MTR test rpl.rpl_semi_sync_no_missed_ack_after_add_slave fails with
rpl.rpl_semi_sync_no_missed_ack_after_add_slave 'stmt' w12 [ fail ]
|
Test ended at 2024-06-10 12:37:26
|
|
CURRENT_TEST: rpl.rpl_semi_sync_no_missed_ack_after_add_slave
|
mysqltest: At line 77: server_3 should have sent semi-sync ACK to primary
|
|
The result from queries just before the failure was:
|
< snip >
|
set @old_dbug= @@global.debug_dbug;
|
set global rpl_semi_sync_slave_enabled= 1;
|
set global debug_dbug="+d,simulate_delay_semisync_slave_reply";
|
include/start_slave.inc
|
connection server_3;
|
include/stop_slave.inc
|
set @old_enabled= @@global.rpl_semi_sync_slave_enabled;
|
set global rpl_semi_sync_slave_enabled= 1;
|
include/start_slave.inc
|
# Ensure primary recognizes both replicas are semi-sync
|
connection server_1;
|
connection server_1;
|
create table t1 (a int);
|
connection server_2;
|
# Verifying server_2 did not send ACK
|
connection server_3;
|
# Verifying server_3 did send ACK
|
SHOW STATUS LIKE 'rpl_semi_sync_slave_send_ack';
|
Variable_name Value
|
Rpl_semi_sync_slave_send_ack 1
|