Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
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.
Attachments
Issue Links
- relates to
-
MDEV-17867 Make RESET MASTER throw GTID-related warning if gtid_slave_pos is set
- Open
-
MDEV-10279 gtid_current_pos is not updated with slave transactions from old master
- Open
-
MDEV-17156 Local transactions on a Slave don't update GTID's gtid_current_pos after RESET MASTER on Slave (master_use_gtid value is not relevant)
- Closed
-
MDEV-17368 RESET MASTER doesn't completely reset gtid_current_pos
- Closed
-
MDEV-17370 Create method to purge a specific domain from gtid_binlog_pos
- Closed