[MDEV-21031] rpl_semi_sync_after_sync_row result mismatch Created: 2019-11-11  Updated: 2021-01-12  Resolved: 2021-01-12

Status: Closed
Project: MariaDB Server
Component/s: Replication, Tests
Affects Version/s: 10.3, 10.4
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Andrei Elkin Assignee: Andrei Elkin
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MDEV-22008 rpl.rpl_semi_sync fails with wrong v... Closed
Relates
relates to MDEV-14366 rpl.rpl_semi_sync_after_sync, rpl.rpl... Closed

 Description   

the failure signature is different from MDEV-14366:
CURRENT_TEST: rpl.rpl_semi_sync_after_sync_row
— /usr/share/mysql-test/suite/rpl/r/rpl_semi_sync_after_sync_row.result 2019-11-11 14:39:59.000000000 +0000
+++ /dev/shm/var/3/log/rpl_semi_sync_after_sync_row.reject 2019-11-11 16:03:20.590071576 +0000
@@ -407,7 +407,7 @@
[ Semi-sync status on master should be ON ]
show status like 'Rpl_semi_sync_master_clients';
Variable_name Value
-Rpl_semi_sync_master_clients 0
+Rpl_semi_sync_master_clients 1
show status like 'Rpl_semi_sync_master_status';
Variable_name Value
Rpl_semi_sync_master_status ON

The most probable reason is no synchronization of the master dump thread exit in the test.
Generated at Thu Feb 08 09:04:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.