# Static XDR configuration When you configure XDR statically, all XDR-related parameters are included in the Aerospike configuration file, as shown in [Basic static XDR stanza](#basic-static-xdr-stanza). ::: note - Aerospike recommends configuring XDR dynamically so that all nodes start shipping at the same time. For dynamic configuration instructions, see [Dynamic XDR configuration](https://aerospike.com/docs/database/8.0.0/manage/xdr/dynamic-xdr). - For a theoretical and architectural overview, see [XDR Architecture](https://aerospike.com/docs/database/8.0.0/learn/architecture/xdr). ::: ### Terminology - _Shipping_ refers to sending data from one datacenter (DC) to another. - A cluster from which records are shipped is a _source_ cluster. - A cluster to which records are shipped is a _destination_ cluster. ### Version changes - XDR does not impose any version requirement across datacenters. - Starting with Database 7.2.0, [`ship-versions-policy`](https://aerospike.com/docs/database/reference/config#xdr__ship-versions-policy) controls how XDR ships versions of modified records when facing lag between the source cluster and a destination. - [`ship-versions-interval`](https://aerospike.com/docs/database/reference/config#xdr__ship-versions-interval) specifies a time window in seconds within which XDR is allowed to skip versions. - Starting with Database 5.7.0, the XDR subsystem always accepts dynamic configuration commands because it is always initialized even if XDR is not configured statically. - Prior to Database 5.7.0, the XDR subsystem must be configured statically with at least one datacenter. For information, see [Static XDR configuration](https://aerospike.com/docs/database/8.0.0/manage/xdr/static-xdr). ## Basic static XDR stanza The basic `xdr` stanza of the configuration file uses `xdr`, `dc`, `node-address-port`, and `namespace` to: - Enable XDR - Define target datacenters, including IP addresses and ports of cluster nodes - Specify which namespaces to ship Terminal window ```bash xdr { dc dataCenter1 { node-address-port someIpAddress1 somePort1 namespace nameSpaceName1A { } namespace nameSpaceName1B { // optional - can be all empty bin-policy enable-compression forward ignore-expunges max-throughput 50000 transaction-queue-limit 32768 write-policy remote-namespace ship-only-specified-sets // if ship-only-specified-sets set to true ship-set ship-set // refer to the configuration reference manual // for the full list of optional parameters ... } } dc dataCenter2 { node-address-port namespace nameSpaceName2A { ... } namespace nameSpaceName2B { ... } } ... } ``` ### Parameter description | Parameter | Default value | Description | | --- | --- | --- | | `xdr` | No value is required. | Enables XDR and encloses all other XDR-related parameters. | | [`dc`](https://aerospike.com/docs/database/reference/config#xdr__dc) | None | Declare a variable name for the datacenter. The `xdr` stanza can include a maximum of 64 `dc` sub-stanzas. | | [`node-address-port`](https://aerospike.com/docs/database/reference/config#xdr__node-address-port) | None | Specifies the IP address and port of a node in the remote datacenter. The `dc` sub-stanza can include multiple `node-address-port` specifications. Most of these examples show only one `node-address-port`. The port specification can be followed by a Transport Layer Security (TLS) variable name you define. See [Securing XDR with access control, LDAP, and TLS](https://aerospike.com/docs/database/8.0.0/manage/xdr/security). | | [`namespace`](https://aerospike.com/docs/database/reference/config#xdr__namespace) | None | Specifies the name of the namespace data to ship to the remote datacenters. The `dc` stanza can include multiple `namespace` declarations. The [`remote-namespace`](https://aerospike.com/docs/database/reference/config#xdr__remote-namespace) parameter is required only if the `namespace` needs to be replicated to a different namespace. | ### Global naming convention for namespaces We recommend that you develop a global plan or naming convention for namespaces on all your clusters that participate in XDR. If you intend to use namespace mapping, especially take into account the restrictions described in [Namespace mapping](#namespace-mapping) with `remote-namespace`. Global naming conventions can help clarify the purposes and locations of namespaces in your global deployment, avoid violating naming restrictions, and minimize confusion due to a misunderstanding of, or lack of knowledge of, existing namespaces or namespace mappings. ### Namespace mapping In Database 5.2.0 and later, a namespace can be shipped to a remote namespace with a different name. In earlier versions, the namespace names must match. See [`remote-namespace`](https://aerospike.com/docs/database/reference/config#xdr__remote-namespace) for details. Terminal window ```bash xdr { dc DC1 { node-address-port 10.0.0.1 3000 namespace A { # Map local namespace A to remote namespace B remote-namespace B } } } ``` ## Example configuration parameters for XDR topologies This section presents configuration file parameters that correspond to different supported topologies described in [XDR Architecture](https://aerospike.com/docs/database/8.0.0/learn/architecture/xdr). Only the [basic XDR stanzas](https://aerospike.com/docs/database/8.0.0/manage/xdr/static-xdr/#basic-static-xdr-stanza) are shown, with no optional parameters. ### Active-passive In active-passive topology, data are written to only a single node and then shipped to other datacenters. - [Datacenter A ships to B at 10.2.0.2](#tab-panel-1128) - [Datacenter B at 10.2.0.2](#tab-panel-1129) Terminal window ```bash xdr { dc B { node-address-port 10.2.0.2 3000 namespace someNameSpaceName { ... } } } ``` Terminal window ```bash There is no configuration needed on datacenter B. ``` ### Mesh (active-active) In the following examples, each datacenter ships to all the others but not to itself. - [Datacenter A at 10.0.0.1](#tab-panel-1130) - [Datacenter B at 10.2.0.2](#tab-panel-1131) - [Datacenter C at 10.3.0.3](#tab-panel-1132) Terminal window ```bash xdr { dc B { node-address-port 10.2.0.2 3000 namespace someNameSpaceName { ... } } dc C { node-address-port 10.3.0.3 3000 namespace someNameSpaceName { ... } } } ``` Terminal window ```bash xdr { dc A { node-address-port 10.0.0.1 3000 namespace someNameSpaceName { ... } } dc C { node-address-port 10.3.0.3 3000 namespace someNameSpaceName { ... } } } ``` Terminal window ```bash xdr { dc A { node-address-port 10.0.0.1 3000 namespace someNameSpaceName { ... } } dc B { node-address-port 10.2.0.2 3000 namespace someNameSpaceName { ... } } } ``` ### Mesh with bin-convergence (active-active) In this example, each datacenter ships to all the others with bin-convergence feature turned on. ::: note - [`src-id`](https://aerospike.com/docs/database/reference/config#xdr__src-id) must be different in all the datacenters. - [`conflict-resolve-writes`](https://aerospike.com/docs/database/reference/config#namespace__conflict-resolve-writes) must be set to `true` in the namespace-level in all datacenters. - [`bin-policy`](https://aerospike.com/docs/database/reference/config#xdr__bin-policy) must not be `all`. ::: - [Datacenter A at 10.0.0.1](#tab-panel-1133) - [Datacenter B at 10.2.0.2](#tab-panel-1134) - [Datacenter C at 10.3.0.3](#tab-panel-1135) Terminal window ```bash namespace { ... conflict-resolve-writes true } xdr { src-id 1 dc B { node-address-port 10.2.0.2 3000 namespace someNameSpaceName { ... bin-policy only-changed ship-bin-luts true } } dc C { node-address-port 10.3.0.3 3000 namespace someNameSpaceName { ... bin-policy only-changed ship-bin-luts true } } } ``` Terminal window ```bash namespace { ... conflict-resolve-writes true } xdr { src-id 2 dc A { node-address-port 10.0.0.1 3000 namespace someNameSpaceName { ... bin-policy only-changed ship-bin-luts true } } dc C { node-address-port 10.3.0.3 3000 namespace someNameSpaceName { ... bin-policy only-changed ship-bin-luts true } } } ``` Terminal window ```bash namespace { ... conflict-resolve-writes true } xdr { src-id 3 dc A { node-address-port 10.0.0.1 3000 namespace someNameSpaceName { ... bin-policy only-changed ship-bin-luts true } } dc B { node-address-port 10.2.0.2 3000 namespace someNameSpaceName { ... bin-policy only-changed ship-bin-luts true } } } ``` ### Linear chain In linear chain topology, data is shipped in a straight line from one datacenter to another, and another. In the following example, in Datacenter B, `forward true` is needed to ship records from Datacenter B to Datacenter C. To avoid a loop, Datacenter C must not point back to A. - [Datacenter A at 10.0.0.1 ships to B at 10.2.0.2](#tab-panel-1136) - [Datacenter B at 10.2.0.2 ships to C at 10.3.0.3](#tab-panel-1137) - [Datacenter C at 10.3.0.3](#tab-panel-1138) Terminal window ```bash xdr { dc B { node-address-port 10.2.0.2 3000 namespace someNameSpaceName { ... } } } ``` Terminal window ```bash xdr { dc C { node-address-port 10.3.0.3 3000 namespace someNameSpaceName { forward true ... } } } ``` ```plaintext There is no configuration needed on datacenter C. ``` ### Star In the following example, Datacenter A ships to all other datacenters, with no shipment between those other datacenters. **Datacenter A at 10.0.0.1** Terminal window ```bash xdr { dc B { node-address-port 10.2.0.2 3000 namespace someNameSpaceName { ... } } dc C { node-address-port 10.3.0.3 3000 namespace someNameSpaceName { ... } } dc D { node-address-port 10.4.0.4 3000 namespace someNameSpaceName { ... } } dc E { node-address-port 10.5.0.5 3000 namespace someNameSpaceName { ... } } } ``` ::: note In the star configuration, there is no configuration needed on datacenters B, C, D, and E. ::: ## More XDR information - [Set policy](https://aerospike.com/docs/database/8.0.0/manage/xdr/set-policy) - [Bin policy](https://aerospike.com/docs/database/8.0.0/manage/xdr/bin-policy) - [Write policy](https://aerospike.com/docs/database/8.0.0/manage/xdr/write-policy) - [Bin convergence](https://aerospike.com/docs/database/8.0.0/manage/xdr/convergence) - [Filters](https://aerospike.com/docs/database/8.0.0/manage/xdr/filters) - [Lifecycle of XDR record shipment with metrics](https://aerospike.com/docs/database/8.0.0/manage/xdr/lifecycle) - [Compression, record forwarding, and deleted records](https://aerospike.com/docs/database/8.0.0/manage/xdr/comp-fwd-deletes) - [Securing with access control, LDAP, and TLS](https://aerospike.com/docs/database/8.0.0/manage/xdr/security) - [Reference XDR parameters and metrics](https://aerospike.com/docs/database/8.0.0/manage/xdr/parameters)