Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.5.1, 10.3(EOL), 10.4(EOL), 10.5
-
None
-
kvm-rpm-centos73-amd64
Description
CURRENT_TEST: rpl.rpl_semi_sync
|
--- /usr/share/mysql-test/suite/rpl/r/rpl_semi_sync.result 2020-03-23 00:20:13.000000000 +0000
|
+++ /dev/shm/var/2/log/rpl_semi_sync.reject 2020-03-23 01:42:52.965487725 +0000
|
@@ -177,7 +177,7 @@
|
Rpl_semi_sync_master_yes_tx 14
|
show status like 'Rpl_semi_sync_master_clients';
|
Variable_name Value
|
-Rpl_semi_sync_master_clients 0
|
+Rpl_semi_sync_master_clients 1
|
[ semi-sync replication of these transactions will fail ]
|
insert into t1 values (500);
|
[ master status should be OFF ] |
Attachments
Issue Links
- duplicates
-
MDEV-11220 rpl.rpl_semi_sync failed in buildbot, result mismatch, Rpl_semi_sync_master_status on/off
-
- Closed
-
-
MDEV-21031 rpl_semi_sync_after_sync_row result mismatch
-
- Closed
-
- is duplicated by
-
MDEV-14366 rpl.rpl_semi_sync_after_sync, rpl.rpl_semi_sync_after_sync_row failed in buildbot with wrong result
-
- Closed
-
on the current 10.3 1df1a6392477ad211b2 : http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-rhel8-ppc64le/builds/1358/steps/mtr/logs/stdio
rpl.rpl_semi_sync 'innodb,mix' w2 [ fail ]
Test ended at 2020-07-02 06:30:10
CURRENT_TEST: rpl.rpl_semi_sync
--- /usr/share/mysql-test/suite/rpl/r/rpl_semi_sync.result 2020-07-02 03:54:53.000000000 +0000
+++ /dev/shm/var/2/log/rpl_semi_sync.reject 2020-07-02 06:30:09.730420484 +0000
@@ -406,7 +406,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
mysqltest: Result content mismatch