Configure the Aerospike XDR Proxy
note
Config differences for the HTTP (pre-5.0) XDR-Proxy will be highlighted, if there are any.
Aerospike database setup
The XDR-Proxy requires configuring Aerospike database to push updates and record deletes to the proxy via change notification.
XDR Proxy configuration
The XDR-Proxy is configured via the /etc/aerospike-xdr-proxy/aerospike-xdr-proxy.yml
YAML formatted configuration file.
The configuration file has the following sections:
- service - configures the connector's listening ports, TLS and network interface.
- aerospike - configures Aerospike destination nodes.
- logging - configures the destination and level for the connectors logs.
XDR 5.0 connector wire protocol
A sample configuration is shown below with
service:
port: 8080
aerospike:
seeds:
- 192.168.2.3:
port: 8080
socket-timeout: 1000
total-timeout: 1000
logging:
enable-console-logging: true
file: /var/log/aerospike-xdr-proxy/aerospike-xdr-proxy.log
HTTP based connector configuration
Requires XDR Proxy version 2.0.0
or higher.
service:
port: 8080
protocol: HTTP_2
aerospike:
seeds:
- 192.168.2.3:
port: 8080
socket-timeout: 1000
total-timeout: 1000
logging:
enable-console-logging: true
file: /var/log/aerospike-xdr-proxy/aerospike-xdr-proxy.log