Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
10.2.4-4, 10.2.4-1, 10.3.1-2, 10.2.10, 10.2.11, 10.1.30, 10.2.12
Description
The MariaDB GTID is currently not transferred to other nodes in the cluster. As a result,
receiving nodes simply use the current gtid_domain_id (or wsrep_gitd_domain_id in 10.1)
and server id to tag the incoming transactions along with galera-assigned sequence number.
Attachments
Issue Links
- causes
-
MDEV-6866 Ensure consistency of sequence number in Galera GTID Replication
- Closed
-
MDEV-8458 Galera Cluster replication stream doesn't pass along MariaDB's GTID
- Closed
-
MDEV-10227 MariaDB Galera cluster gtid's falling out of sync inspite of setting wsrep_gtid_mode=ON
- Closed
-
MDEV-13431 wsrep_gtid_mode uses wrong GTID for transaction committed by slave thread
- Closed
- includes
-
MDEV-14323 Example mtr test for 2 clusters
- Closed
- is blocked by
-
MDEV-9856 wsrep_gtid_mode requires nodes to have the same log_bin path
- Closed
- relates to
-
MDEV-7984 Galera doesn't ignore duplicates properly with GTID replication
- Closed
-
MDEV-9107 GTID Slave Pos of untrack domain ids being updated
- Closed
-
MDEV-9315 Xid is only shown for RBR events
- Closed
-
MDEV-14153 Implicitly dropped temporary tables cause GTID drift in Galera cluster
- Closed
-
MDEV-20769 MASTER_GTID_WAIT to work for replicated galera GTIDS
- Open
-
MXS-4819 Failover for async replication between 2 galera cluster
- Open
-
MDEV-9855 log_slave_updates is required for wsrep_gtid_mode
- Closed
-
MDEV-20715 Implement system variable to disallow local GTIDs in Galera
- Closed
-
MXS-2787 Incorrect implementation of Galera replication
- Closed
- links to