XDR forwarding per namespace

Knowledge Base XDR
1

The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.

Synopsis:

NOTE: Valid from 3.3.26

Configure forwarding per namespace.

In cases where you use forwarding you might decided to forward only a specific namespace and not all of them which is the default behavior. Here is an example configuration for such a setup.

Scenario A → B → C

DC A is using XDR to send its data to DC B. DC B only wants to forward one namespace (test) to DC C. XDR Configuration in B will be:

xdr {
        enable-xdr true
        namedpipe-path /tmp/xdr_pipe
        digestlog-path /opt/aerospike/data/digestlog 100G
        errorlog-path /var/log/aerospike/asxdr.log
        local-node-port 3000
        info-port 3004
        datacenter dc1 {
                dc-node-address-port  192.168.204.138 3000
        }
}

namespace test {
        replication-factor 2
        memory-size 1G
        default-ttl 30d
        enable-xdr true
        xdr-remote-datacenter dc1
        storage-engine memory
        ns-forward-xdr-writes true
}

namespace test2 {
        replication-factor 2
        memory-size 1G
        default-ttl 30d
        storage-engine memory
}

Applies To

Server prior to v. 5.0