gtid_domain_id

Overview

Used with global transaction ID to identify logically independent replication streams. When events can propagate through multiple parallel paths (for example multiple masters), each independent source server must use a distinct domain_id. For simple tree-shaped replication topologies, it can be left at its default, 0.

USAGE

DETAILS

SYNONYMS

SCHEMA

PARAMETERS

Command-line

--gtid_domain_id=#

Configuration file

Supported

Dynamic

Yes

Scope

Global, Session

Data Type

INT UNSIGNED

Minimum Value

0

Maximum Value

4294967295

Product Default Value

0

SKYSQL

Cloud

SkySQL Topology

ES Ver

Service Default

AWS

Multi-Node Analytics

10.6

139601

Single Node Analytics

10.6

139500

Replicated Transactions

10.4

139200

10.5

139100

10.6

139000

Single Node Transactions

10.4

138700

10.5

138600

10.6

138500

GCP

Multi-Node Analytics

10.6

138401

Single Node Analytics

10.6

138300

Replicated Transactions

10.4

137800

10.5

137900

10.6

138000

Single Node Transactions

10.4

137500

10.5

137600

10.6

137700

Cloud

SkySQL Topology

ES Ver

Service Default

AWS

ColumnStore Data Warehouse

10.6

139601

Enterprise Server With Replica(s)

10.4

139200

10.5

139100

10.6

139000

Enterprise Server Single Node

10.4

138700

10.5

138600

10.6

138500

GCP

ColumnStore Data Warehouse

10.6

138401

Enterprise Server With Replica(s)

10.4

137800

10.5

137900

10.6

138000

Enterprise Server Single Node

10.4

137500

10.5

137600

10.6

137700

PRIVILEGES

EXAMPLES

ERROR HANDLING

FEATURE INTERACTION

RESPONSES

DIAGNOSIS

ISO 9075:2016

CHANGE HISTORY

Release Series

History

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1.

10.6 Community

  • Present starting in MariaDB Community Server 10.6.0.

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.5 Community

  • Present starting in MariaDB Community Server 10.5.0.

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1.

10.4 Community

  • Present starting in MariaDB Community Server 10.4.0.

10.3 Enterprise

  • Present starting in MariaDB Enterprise Server 10.3.16-1.

10.3 Community

  • Present starting in MariaDB Community Server 10.3.0.

10.2 Enterprise

  • Present starting in MariaDB Enterprise Server 10.2.25-1.

10.2 Community

  • Present starting in MariaDB Community Server 10.2.0.

Release Series

History

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1.

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1.

EXTERNAL REFERENCES