1 of 1

Using MariaDB GTIDs with MariaDB Galera Cluster

MariaDB Galera Cluster has partial GTID support via wsrep_gtid_mode, which associates write-sets with globally unique GTIDs that remain consistent across cluster nodes in most cases.

MariaDB's are very useful when used with , which is primarily what that feature was developed for. , on the other hand, was developed by Codership for all MySQL and MariaDB variants, and the initial development of the technology pre-dated MariaDB's implementation. As a side effect, (at least until ) only partially supports MariaDB's implementation.

Galera Cluster has its own that is substantially different from . However, it would still be beneficial if was able to associate a Galera Cluster write set with a that is globally unique but that is also consistent for that write set on each cluster node.

MariaDB supports .

MariaDB has a feature called wsrep GTID mode. When this mode is enabled, MariaDB uses some tricks to try to associate each Galera Cluster write set with a that is globally unique, but that is also consistent for that write set on each cluster node. These tricks work in some cases, but

Using MariaDB GTIDs with MariaDB Galera Cluster

MariaDB Galera Cluster has partial GTID support via wsrep_gtid_mode, which associates write-sets with globally unique GTIDs that remain consistent across cluster nodes in most cases.

MariaDB supports .

wsrep_gtid_mode=ON needs to be set on all nodes in the cluster.
wsrep_gtid_domain_id needs to be set to the same value on all nodes in a given cluster, so that each cluster node uses the same domain when assigning for Galera Cluster's write sets. When replicating between two clusters, each cluster should have this set to a different value, so that each cluster uses different domains when assigning for their write sets.
needs to be enabled on all nodes in the cluster. See MDEV-9855.
needs to be set to the same path on all nodes in the cluster. See .

should be set to a different value on all nodes in a given cluster, and each of these values should be different than the configured wsrep_gtid_domain_id value. This is to prevent a node from using the same domain used for Galera Cluster's write sets when assigning for non-Galera transactions, such as DDL executed with wsrep_sst_method=RSU set or DML executed with wsrep_on=OFF set.

If a Galera Cluster node is also a , then that node's will be applying transactions that it replicates from its replication master. If the node has set, then each transaction that the applies will also generate a Galera Cluster write set that is replicated to the rest of the nodes in the cluster.

The node acting as slave includes the transaction's original Gtid_Log_Event in the replicated write set, so all nodes should associate the write set with its original GTID. See MDEV-13431.

Using MariaDB GTIDs with MariaDB Galera Cluster

Using MariaDB GTIDs with MariaDB Galera Cluster

GTID Support for Write Sets Replicated by Galera Cluster

Wsrep GTID Mode

Enabling Wsrep GTID Mode

GTIDs for Transactions Applied by Slave Thread