[MDEV-11862] rpl.rpl_semi_sync_event_after_sync 'fails if there is no semisync plugin Created: 2017-01-21  Updated: 2021-06-10  Resolved: 2021-02-15

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.1
Fix Version/s: 10.2.38, 10.3.29, 10.4.19, 10.5.10

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Alice Sherepa
Resolution: Fixed Votes: 0
Labels: None


 Description    

rpl.rpl_semi_sync_event_after_sync 'mix,xtradb' [ fail ]
 
        Test ended at 2017-01-21 16:54:15
 
 
 
CURRENT_TEST: rpl.rpl_semi_sync_event_after_sync
 
mysqltest: At line 1: query 'set global rpl_semi_sync_master_wait_point=AFTER_SYNC' failed: 1193: Unknown system variable 'rpl_semi_sync_master_wait_point'
 
 
 
The result from queries just before the failure was:
 
set global rpl_semi_sync_master_wait_point=AFTER_SYNC;

The test first attempts to set rpl_semi_sync_master_wait_point and then sources rpl_semi_sync_event.test which, in turn, sources include/have_semisync.inc which checks whether the plugin exists.

The easy way to fix it is to source include/have_semisync.inc from rpl_semi_sync_event_after_sync itself. There might be smarter ways to do the same.



 Comments   
Comment by Elena Stepanova [ 2021-01-25 ]

alice

Please do whatever you want with it. I think 10.2 was the last version where the plugin was a library, so probably it's not even applicable to 10.3 (or maybe it is, for special builds, but MTR tests don't usually work for customized builds anyway).

Generated at Thu Feb 08 07:53:14 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.