[MDEV-17853] Document that gtid_binlog_pos can lag behind gtid_current_pos after RESET MASTER Created: 2018-11-27  Updated: 2020-08-25  Resolved: 2018-11-27

Status: Closed
Project: MariaDB Server
Component/s: Documentation - Support, Replication
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Kenneth Dyer (Inactive)
Resolution: Fixed Votes: 0
Labels: GTID

Issue Links:
Relates
relates to MDEV-17867 Make RESET MASTER throw GTID-related ... Open
relates to MDEV-10279 gtid_current_pos is not updated with ... Open
relates to MDEV-17156 Local transactions on a Slave don't u... Closed
relates to MDEV-17368 RESET MASTER doesn't completely reset... Closed
relates to MDEV-17370 Create method to purge a specific dom... Closed

 Description   

gtid_current_pos is the union of gtid_binlog_pos and gtid_slave_pos. RESET MASTER resets gtid_binlog_pos, but it does not reset gtid_slave_pos. This means that new GTIDs added to gtid_binlog_pos can actually lag behind the GTIDs in gtid_current_pos after RESET MASTER is executed if gtid_slave_pos is set and if it contains GTIDs in the same domains as the ones in gtid_binlog_pos. This should be added to the documentation.

See MDEV-17156 for details.
Generated at Thu Feb 08 08:39:36 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.