[MDEV-24235] Unnessary errror out to SET gtid_slave_pos in gtid_strict_mode Created: 2020-11-17  Updated: 2020-11-17  Resolved: 2020-11-17

Status: Closed
Project: MariaDB Server
Component/s: Replication
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Andrei Elkin Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: gtid

Issue Links:
Duplicate
duplicates MDEV-24234 gtid_strict_mode is not compatible wi... Open

 Description   

When gtid_strict_mode = ON an attempt to SET @@global.gtid_slave_pos to a value
not containing gtid domains from the slave's gtid_binlog_pos is reacted with an error, like

[test]> set @@global.gtid_slave_pos='0-1-2';
ERROR 1948 (HY000): Specified value for @@gtid_slave_pos contains no value for replication domain 99. This conflicts with the binary log which contains GTID 99-2-1. If MASTER_GTID_POS=CURRENT_POS is used, the binlog position will override the new value of @@gtid_slave_pos

The error message itself makes clear that the error is mere potential and there's no issue
when MASTER_GTID_POS = SLAVE_POS will be specified later.

The error issuing there should wait until MASTER_GTID_POS value gets known.



 Comments   
Comment by Geoff Montee (Inactive) [ 2020-11-17 ]

Oops. I already created MDEV-24234 about this.

Generated at Thu Feb 08 09:28:27 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.